From: Pavel Begunkov <[email protected]>
To: Sudip Mukherjee <[email protected]>,
Jens Axboe <[email protected]>
Cc: [email protected], linux-kernel <[email protected]>
Subject: Re: KASAN: stack-out-of-bounds in iov_iter_revert
Date: Sun, 1 Aug 2021 01:10:35 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CADVatmOf+ZfxXA=LBSUqDZApZG3K1Q8GV2N5CR5KgrJLqTGsfg@mail.gmail.com>
On 7/31/21 7:21 PM, Sudip Mukherjee wrote:
> Hi Jens, Pavel,
>
> We had been running syzkaller on v5.10.y and a "KASAN:
> stack-out-of-bounds in iov_iter_revert" was being reported on it. I
> got some time to check that today and have managed to get a syzkaller
> reproducer. I dont have a C reproducer which I can share but I can use
> the syz-reproducer to reproduce this with v5.14-rc3 and also with
> next-20210730.
Can you try out the diff below? Not a full-fledged fix, but need to
check a hunch.
If that's important, I was using this branch:
git://git.kernel.dk/linux-block io_uring-5.14
diff --git a/fs/io_uring.c b/fs/io_uring.c
index bf548af0426c..fdcd25eca67d 100644
--- a/fs/io_uring.c
+++ b/fs/io_uring.c
@@ -3316,6 +3316,10 @@ static int io_read(struct io_kiocb *req, unsigned int issue_flags)
/* no retry on NONBLOCK nor RWF_NOWAIT */
if (req->flags & REQ_F_NOWAIT)
goto done;
+ if (WARN_ON_ONCE(iter->truncated)) {
+ iov_iter_reexpand(iter, iov_iter_count(iter) + iter->truncated);
+ iter->truncated = 0;
+ }
/* some cases will consume bytes even on error returns */
iov_iter_revert(iter, io_size - iov_iter_count(iter));
ret = 0;
@@ -3455,6 +3459,10 @@ static int io_write(struct io_kiocb *req, unsigned int issue_flags)
kiocb_done(kiocb, ret2, issue_flags);
} else {
copy_iov:
+ if (WARN_ON_ONCE(iter->truncated)) {
+ iov_iter_reexpand(iter, iov_iter_count(iter) + iter->truncated);
+ iter->truncated = 0;
+ }
/* some cases will consume bytes even on error returns */
iov_iter_revert(iter, io_size - iov_iter_count(iter));
ret = io_setup_async_rw(req, iovec, inline_vecs, iter, false);
diff --git a/include/linux/uio.h b/include/linux/uio.h
index 82c3c3e819e0..eff06d139fd4 100644
--- a/include/linux/uio.h
+++ b/include/linux/uio.h
@@ -30,6 +30,7 @@ enum iter_type {
struct iov_iter {
u8 iter_type;
bool data_source;
+ u16 truncated;
size_t iov_offset;
size_t count;
union {
@@ -254,8 +255,10 @@ static inline void iov_iter_truncate(struct iov_iter *i, u64 count)
* conversion in assignement is by definition greater than all
* values of size_t, including old i->count.
*/
- if (i->count > count)
+ if (i->count > count) {
+ i->truncated += i->count - count;
i->count = count;
+ }
}
/*
@@ -264,6 +267,8 @@ static inline void iov_iter_truncate(struct iov_iter *i, u64 count)
*/
static inline void iov_iter_reexpand(struct iov_iter *i, size_t count)
{
+ WARN_ON_ONCE(i->count > count);
+ i->truncated -= count - i->count;
i->count = count;
}
next prev parent reply other threads:[~2021-08-01 0:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-31 18:21 KASAN: stack-out-of-bounds in iov_iter_revert Sudip Mukherjee
2021-08-01 0:10 ` Pavel Begunkov [this message]
2021-08-01 8:52 ` Pavel Begunkov
2021-08-01 20:28 ` Sudip Mukherjee
2021-08-02 11:55 ` Pavel Begunkov
2021-08-03 7:47 ` Sudip Mukherjee
2021-08-03 10:34 ` Pavel Begunkov
2021-08-03 13:18 ` Pavel Begunkov
2021-08-03 14:56 ` Sudip Mukherjee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox