From: syzbot <syzbot+43d0c6eb00a26a41ec60@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 __closure_sync_timeout
Date: Tue, 22 Oct 2024 15:39:04 -0700 [thread overview]
Message-ID: <67182988.050a0220.1e4b4d.007c.GAE@google.com> (raw)
In-Reply-To: <6717a66e.050a0220.10f4f4.0127.GAE@google.com>
syzbot has bisected this issue to:
commit f7643bc9749f270d487c32dc35b578575bf1adb0
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Wed Apr 17 05:26:02 2024 +0000
bcachefs: make btree read errors silent during scan
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1374a640580000
start commit: c2ee9f594da8 KVM: selftests: Fix build on on non-x86 archi..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=10f4a640580000
console output: https://syzkaller.appspot.com/x/log.txt?x=1774a640580000
kernel config: https://syzkaller.appspot.com/x/.config?x=41330fd2db03893d
dashboard link: https://syzkaller.appspot.com/bug?extid=43d0c6eb00a26a41ec60
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12265430580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1105c640580000
Reported-by: syzbot+43d0c6eb00a26a41ec60@syzkaller.appspotmail.com
Fixes: f7643bc9749f ("bcachefs: make btree read errors silent during scan")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-10-22 22:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 13:19 [syzbot] [bcachefs?] INFO: task hung in __closure_sync_timeout syzbot
2024-10-22 22:39 ` syzbot [this message]
2025-01-06 18:27 ` 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=67182988.050a0220.1e4b4d.007c.GAE@google.com \
--to=syzbot+43d0c6eb00a26a41ec60@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