From: syzbot <syzbot+c6fd966ebbdea1e8ff08@syzkaller.appspotmail.com>
To: bfoster@redhat.com, kent.overstreet@linux.dev,
linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] INFO: task hung in bch2_copygc_stop
Date: Tue, 17 Sep 2024 02:51:02 -0700 [thread overview]
Message-ID: <00000000000095b8f806224da030@google.com> (raw)
In-Reply-To: <0000000000006304400619bbfae2@google.com>
syzbot has bisected this issue to:
commit f5095b9f85a1674a92d00e7ab466499a8ba49ce1
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Tue Jan 2 00:42:37 2024 +0000
bcachefs: dev_usage updated by new accounting
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1256e29f980000
start commit: adfc3ded5c33 Merge tag 'for-6.12/io_uring-discard-20240913..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1156e29f980000
console output: https://syzkaller.appspot.com/x/log.txt?x=1656e29f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=6f94136b4da4e897
dashboard link: https://syzkaller.appspot.com/bug?extid=c6fd966ebbdea1e8ff08
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10936a8b980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10bdd7c7980000
Reported-by: syzbot+c6fd966ebbdea1e8ff08@syzkaller.appspotmail.com
Fixes: f5095b9f85a1 ("bcachefs: dev_usage updated by new accounting")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-09-17 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 8:43 [syzbot] [bcachefs?] INFO: task hung in bch2_copygc_stop syzbot
2024-09-16 9:28 ` syzbot
2024-09-17 9:51 ` syzbot [this message]
2025-07-23 1:17 ` Forwarded: syzbot
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=00000000000095b8f806224da030@google.com \
--to=syzbot+c6fd966ebbdea1e8ff08@syzkaller.appspotmail.com \
--cc=bfoster@redhat.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@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 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).