From: Jens Axboe <axboe@kernel.dk>
To: syzbot <syzbot+3254bc44113ae1e331ee@syzkaller.appspotmail.com>,
io-uring@vger.kernel.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: KASAN: invalid-free in io_sqe_files_unregister
Date: Sun, 10 Nov 2019 08:46:06 -0700 [thread overview]
Message-ID: <e3ed8352-23ca-246d-088c-878f9da82c76@kernel.dk> (raw)
In-Reply-To: <000000000000e11df90596fc9955@google.com>
On 11/10/19 4:49 AM, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit 65e19f54d29cd8559ce60cfd0d751bef7afbdc5c
> Author: Jens Axboe <axboe@kernel.dk>
> Date: Sat Oct 26 13:20:21 2019 +0000
>
> io_uring: support for larger fixed file sets
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=154f483ce00000
> start commit: 5591cf00 Add linux-next specific files for 20191108
> git tree: linux-next
> final crash: https://syzkaller.appspot.com/x/report.txt?x=174f483ce00000
> console output: https://syzkaller.appspot.com/x/log.txt?x=134f483ce00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=e1036c6ef52866f9
> dashboard link: https://syzkaller.appspot.com/bug?extid=3254bc44113ae1e331ee
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=116bb33ae00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=173f133ae00000
>
> Reported-by: syzbot+3254bc44113ae1e331ee@syzkaller.appspotmail.com
> Fixes: 65e19f54d29c ("io_uring: support for larger fixed file sets")
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Thanks, I queued up a fix:
https://git.kernel.dk/cgit/linux-block/commit/?h=for-5.5/io_uring&id=fc2a85cb02efd7bdbd09ea5d2d9847937da7bff7
--
Jens Axboe
prev parent reply other threads:[~2019-11-10 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000003659ef0596fa4cae@google.com>
2019-11-10 11:49 ` KASAN: invalid-free in io_sqe_files_unregister syzbot
2019-11-10 15:46 ` Jens Axboe [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=e3ed8352-23ca-246d-088c-878f9da82c76@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+3254bc44113ae1e331ee@syzkaller.appspotmail.com \
--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 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).