From: Pavel Begunkov <asml.silence@gmail.com>
To: syzbot <syzbot+9c3492b27d10dc49ffa6@syzkaller.appspotmail.com>,
axboe@kernel.dk, io-uring@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: use-after-free Read in tctx_task_work (2)
Date: Thu, 19 Aug 2021 21:56:28 +0100 [thread overview]
Message-ID: <a8a25b40-90ef-f366-4f5c-1ec95638d725@gmail.com> (raw)
In-Reply-To: <00000000000008f3c605c9ecd545@google.com>
On 8/19/21 6:25 PM, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch and the reproducer did not trigger any issue
https://git.kernel.dk/cgit/linux-block/commit/?h=for-5.15/io_uring&id=84a8ffdcd42da1f0710819e863a7db4309d4ceac
Ok, looks this patch broke it. I need to look where I'm wrong,
but for now it should be dropped.
>
> Reported-and-tested-by: syzbot+9c3492b27d10dc49ffa6@syzkaller.appspotmail.com
>
> Tested on:
>
> commit: 923ffe35 Revert "io_uring: improve tctx_task_work() ct..
> git tree: https://github.com/isilence/linux.git syztest_ctx_tw
> kernel config: https://syzkaller.appspot.com/x/.config?x=cb4282936412304f
> dashboard link: https://syzkaller.appspot.com/bug?extid=9c3492b27d10dc49ffa6
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1
>
> Note: testing is done by a robot and is best-effort only.
>
--
Pavel Begunkov
prev parent reply other threads:[~2021-08-19 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 8:10 [syzbot] KASAN: use-after-free Read in tctx_task_work (2) syzbot
2021-08-19 10:03 ` Pavel Begunkov
2021-08-19 10:44 ` syzbot
2021-08-19 11:13 ` Pavel Begunkov
2021-08-19 17:25 ` syzbot
2021-08-19 20:56 ` Pavel Begunkov [this message]
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 \
--in-reply-to=a8a25b40-90ef-f366-4f5c-1ec95638d725@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+9c3492b27d10dc49ffa6@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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;
as well as URLs for NNTP newsgroup(s).