From: syzbot <syzbot+21e6887c0be14181206d@syzkaller.appspotmail.com>
To: asml.silence@gmail.com, axboe@kernel.dk, clm@fb.com,
dsterba@suse.com, fgheet255t@gmail.com, io-uring@vger.kernel.org,
josef@toxicpanda.com, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
wqu@suse.com
Subject: Re: [syzbot] INFO: task hung in io_uring_cancel_generic (2)
Date: Wed, 08 Dec 2021 14:12:09 -0800 [thread overview]
Message-ID: <000000000000fadd4905d2a9c7e8@google.com> (raw)
In-Reply-To: <000000000000e016c205d1025f4c@google.com>
syzbot has bisected this issue to:
commit 741ec653ab58f5f263f2b6df38157997661c7a50
Author: Qu Wenruo <wqu@suse.com>
Date: Mon Sep 27 07:22:01 2021 +0000
btrfs: subpage: make end_compressed_bio_writeback() compatible
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=103f2ae5b00000
start commit: cd8c917a56f2 Makefile: Do not quote value for CONFIG_CC_IM..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=123f2ae5b00000
console output: https://syzkaller.appspot.com/x/log.txt?x=143f2ae5b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=5247c9e141823545
dashboard link: https://syzkaller.appspot.com/bug?extid=21e6887c0be14181206d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1218dce1b00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16f91d89b00000
Reported-by: syzbot+21e6887c0be14181206d@syzkaller.appspotmail.com
Fixes: 741ec653ab58 ("btrfs: subpage: make end_compressed_bio_writeback() compatible")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-12-08 22:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 21:03 [syzbot] INFO: task hung in io_uring_cancel_generic (2) syzbot
2021-12-08 0:04 ` syzbot
2021-12-09 15:58 ` Jens Axboe
2021-12-09 16:56 ` syzbot
2021-12-08 22:12 ` syzbot [this message]
2021-12-09 2:51 ` Josef Bacik
2021-12-09 3:45 ` 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=000000000000fadd4905d2a9c7e8@google.com \
--to=syzbot+21e6887c0be14181206d@syzkaller.appspotmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=fgheet255t@gmail.com \
--cc=io-uring@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wqu@suse.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.