From: syzbot <syzbot+050e797ad21ccc3f5d1a@syzkaller.appspotmail.com>
To: bfoster@redhat.com, kent.overstreet@linux.dev,
linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org,
lizhi.xu@windriver.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] possible deadlock in bch2_gc_mark_key
Date: Fri, 21 Jun 2024 15:17:02 -0700 [thread overview]
Message-ID: <0000000000007a267d061b6dca15@google.com> (raw)
In-Reply-To: <000000000000aa7cb106196f6883@google.com>
syzbot has bisected this issue to:
commit 103304021e54bfb5cab9ba04cd5ef0dc2bf33888
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Sat Apr 20 02:44:12 2024 +0000
bcachefs: Move gc of bucket.oldest_gen to workqueue
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=162879ea980000
start commit: 50736169ecc8 Merge tag 'for-6.10-rc4-tag' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=112879ea980000
kernel config: https://syzkaller.appspot.com/x/.config?x=12f98862a3c0c799
dashboard link: https://syzkaller.appspot.com/bug?extid=050e797ad21ccc3f5d1a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=144f0a61980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17cab6a6980000
Reported-by: syzbot+050e797ad21ccc3f5d1a@syzkaller.appspotmail.com
Fixes: 103304021e54 ("bcachefs: Move gc of bucket.oldest_gen to workqueue")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-06-21 22:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 13:22 [syzbot] [bcachefs?] possible deadlock in bch2_gc_mark_key syzbot
2024-06-21 5:31 ` syzbot
2024-06-21 9:34 ` [PATCH] bcachefs: fix " Lizhi Xu
2024-06-22 13:43 ` Kent Overstreet
2024-06-21 8:58 ` [syzbot] Re: [syzbot] [bcachefs?] possible " syzbot
2024-06-21 22:17 ` syzbot [this message]
2024-08-23 22:51 ` [syzbot] " syzbot
[not found] <20240621085812.1588215-1-lizhi.xu@windriver.com>
2024-06-21 9:28 ` [syzbot] [bcachefs?] " 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=0000000000007a267d061b6dca15@google.com \
--to=syzbot+050e797ad21ccc3f5d1a@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=lizhi.xu@windriver.com \
--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.