From: syzbot <syzbot+e51249708aaa9b0e4d2c@syzkaller.appspotmail.com>
To: asml.silence@gmail.com, axboe@kernel.dk, haoxu@linux.alibaba.com,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] general protection fault in __io_file_supports_nowait
Date: Tue, 31 Aug 2021 23:41:08 -0700 [thread overview]
Message-ID: <000000000000ef423f05cae95929@google.com> (raw)
In-Reply-To: <0000000000006d354305cae2253f@google.com>
syzbot has bisected this issue to:
commit a8295b982c46d4a7c259a4cdd58a2681929068a9
Author: Hao Xu <haoxu@linux.alibaba.com>
Date: Fri Aug 27 09:46:09 2021 +0000
io_uring: fix failed linkchain code logic
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=147a8045300000
start commit: b91db6a0b52e Merge tag 'for-5.15/io_uring-vfs-2021-08-30' ..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=167a8045300000
console output: https://syzkaller.appspot.com/x/log.txt?x=127a8045300000
kernel config: https://syzkaller.appspot.com/x/.config?x=961d30359ac81f8c
dashboard link: https://syzkaller.appspot.com/bug?extid=e51249708aaa9b0e4d2c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10a91625300000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12512291300000
Reported-by: syzbot+e51249708aaa9b0e4d2c@syzkaller.appspotmail.com
Fixes: a8295b982c46 ("io_uring: fix failed linkchain code logic")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-09-01 6:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 22:05 [syzbot] general protection fault in __io_file_supports_nowait syzbot
2021-09-01 2:00 ` syzbot
2021-09-01 2:08 ` Jens Axboe
2021-09-01 3:34 ` syzbot
2021-09-01 6:41 ` syzbot [this message]
2021-10-06 17:54 ` syzbot
2021-10-06 17:55 ` Jens Axboe
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=000000000000ef423f05cae95929@google.com \
--to=syzbot+e51249708aaa9b0e4d2c@syzkaller.appspotmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=haoxu@linux.alibaba.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.