From: syzbot <syzbot+cb91f22d8a581fc19edf@syzkaller.appspotmail.com>
To: =syzbot@syzkaller.appspotmail.com, kartikey406@gmail.com,
kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
torvalds@linux-foundation.org
Subject: Re: [syzbot] [bcachefs?] INFO: task hung in bch2_seek_pagecache_hole (3)
Date: Fri, 24 Oct 2025 20:55:03 -0700 [thread overview]
Message-ID: <68fc4a17.a70a0220.3bf6c6.01af.GAE@google.com> (raw)
In-Reply-To: <68cb3c24.050a0220.50883.0029.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit f2c61db29f277b9c80de92102fc532cc247495cd
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Mon Sep 29 20:43:52 2025 +0000
Remove bcachefs core code
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13ba53e2580000
start commit: 5aca7966d2a7 Merge tag 'perf-tools-fixes-for-v6.17-2025-09..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=f5b21423ca3f0a96
dashboard link: https://syzkaller.appspot.com/bug?extid=cb91f22d8a581fc19edf
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10052e42580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: Remove bcachefs core code
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-10-25 3:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 22:54 [syzbot] [bcachefs?] INFO: task hung in bch2_seek_pagecache_hole (3) syzbot
2025-09-27 6:53 ` Forwarded: [PATCH] bcachefs: Fix deadlock between fallocate and readahead syzbot
2025-09-27 6:53 ` syzbot
2025-09-27 7:25 ` Forwarded: [PATCH] bcachefs: Fix deadlocks " syzbot
2025-09-27 7:25 ` syzbot
2025-10-25 3:55 ` syzbot [this message]
[not found] <20250927065348.37852-1-kartikey406@gmail.com>
2025-09-27 7:12 ` [syzbot] [bcachefs?] INFO: task hung in bch2_seek_pagecache_hole (3) syzbot
[not found] <20250927072538.39483-1-kartikey406@gmail.com>
2025-09-27 7:49 ` 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=68fc4a17.a70a0220.3bf6c6.01af.GAE@google.com \
--to=syzbot+cb91f22d8a581fc19edf@syzkaller.appspotmail.com \
--cc==syzbot@syzkaller.appspotmail.com \
--cc=kartikey406@gmail.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
/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.