From: syzbot <[email protected]>
To: [email protected], [email protected],
[email protected], [email protected],
[email protected]
Subject: Re: [syzbot] KASAN: stack-out-of-bounds Read in iov_iter_revert
Date: Thu, 12 Aug 2021 13:36:08 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: [email protected]
Tested on:
commit: bff2c168 io_uring: don't retry with truncated iter
git tree: https://github.com/isilence/linux.git truncate
kernel config: https://syzkaller.appspot.com/x/.config?x=730106bfb5bf8ace
dashboard link: https://syzkaller.appspot.com/bug?extid=9671693590ef5aad8953
compiler: Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.1
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2021-08-12 20:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 13:43 [syzbot] KASAN: stack-out-of-bounds Read in iov_iter_revert syzbot
2021-08-12 14:30 ` Pavel Begunkov
2021-08-12 20:36 ` syzbot [this message]
2021-11-03 17:01 ` Lee Jones
2021-11-08 15:29 ` Pavel Begunkov
2021-11-08 15:41 ` Jens Axboe
2021-11-09 13:33 ` Lee Jones
2021-12-15 8:06 ` Lee Jones
2021-12-15 11:16 ` Pavel Begunkov
2021-12-16 17:02 ` Lee Jones
2022-02-22 16:48 ` Lee Jones
2022-03-21 10:52 ` Lee Jones
2022-05-05 14:11 ` linux-stable-5.10-y CVE-2022-1508 of io_uring module Guo Xuenan
2022-05-06 2:16 ` Jens Axboe
2022-05-06 15:57 ` Pavel Begunkov
2022-05-06 16:15 ` Jens Axboe
2022-05-06 18:22 ` Jens Axboe
2022-05-07 9:16 ` Pavel Begunkov
2022-05-07 14:18 ` Jens Axboe
2022-05-08 11:43 ` Pavel Begunkov
2021-08-23 0:24 ` [syzbot] KASAN: stack-out-of-bounds Read in iov_iter_revert Pavel Begunkov
2021-08-23 0:44 ` syzbot
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] \
[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