From: syzbot <syzbot+3587cbbc6e1868796292@syzkaller.appspotmail.com>
To: asml.silence@gmail.com, axboe@kernel.dk, bcrl@kvack.org,
linux-aio@kvack.org, linux-block@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] KASAN: use-after-free Write in io_submit_one
Date: Tue, 07 Dec 2021 21:04:11 -0800 [thread overview]
Message-ID: <000000000000ad0e4105d29b6b0f@google.com> (raw)
In-Reply-To: <0000000000007de81505cfea992f@google.com>
syzbot has bisected this issue to:
commit 54a88eb838d37af930c9f19e1930a4fba6789cb5
Author: Pavel Begunkov <asml.silence@gmail.com>
Date: Sat Oct 23 16:21:32 2021 +0000
block: add single bio async direct IO helper
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1615e2b9b00000
start commit: 04fe99a8d936 Add linux-next specific files for 20211207
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1515e2b9b00000
console output: https://syzkaller.appspot.com/x/log.txt?x=1115e2b9b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=4589399873466942
dashboard link: https://syzkaller.appspot.com/bug?extid=3587cbbc6e1868796292
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17db884db00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14e9eabdb00000
Reported-by: syzbot+3587cbbc6e1868796292@syzkaller.appspotmail.com
Fixes: 54a88eb838d3 ("block: add single bio async direct IO helper")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-12-08 5:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 23:16 [syzbot] KASAN: use-after-free Write in io_submit_one syzbot
2021-12-07 18:49 ` syzbot
2021-12-08 5:04 ` syzbot [this message]
2021-12-08 18:14 ` Pavel Begunkov
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=000000000000ad0e4105d29b6b0f@google.com \
--to=syzbot+3587cbbc6e1868796292@syzkaller.appspotmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=bcrl@kvack.org \
--cc=linux-aio@kvack.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.