From: syzbot <syzbot+20254ae9982bc25a0dc7@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 bchfs_fallocate (2)
Date: Wed, 01 Jan 2025 18:35:02 -0800 [thread overview]
Message-ID: <6775fb56.050a0220.3a8527.0033.GAE@google.com> (raw)
In-Reply-To: <6775a1a9.050a0220.3a8527.002b.GAE@google.com>
syzbot has bisected this issue to:
commit 1d16c605cc55ef26f0c65b362665a6c99080ccbc
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Thu Nov 9 19:22:46 2023 +0000
bcachefs: Disk space accounting rewrite
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1750e8b0580000
start commit: 8155b4ef3466 Add linux-next specific files for 20241220
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=14d0e8b0580000
console output: https://syzkaller.appspot.com/x/log.txt?x=10d0e8b0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9c90bb7161a56c88
dashboard link: https://syzkaller.appspot.com/bug?extid=20254ae9982bc25a0dc7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=170cd0b0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14e432c4580000
Reported-by: syzbot+20254ae9982bc25a0dc7@syzkaller.appspotmail.com
Fixes: 1d16c605cc55 ("bcachefs: Disk space accounting rewrite")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-01-02 2:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 20:12 [syzbot] [bcachefs?] INFO: task hung in bchfs_fallocate (2) syzbot
2025-01-02 2:35 ` syzbot [this message]
2025-08-08 5:39 ` Alan Huang
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=6775fb56.050a0220.3a8527.0033.GAE@google.com \
--to=syzbot+20254ae9982bc25a0dc7@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