From: syzbot <syzbot+de1434c5355cc909b734@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 invalidate_inode_pages2_range (3)
Date: Fri, 28 Feb 2025 16:22:02 -0800 [thread overview]
Message-ID: <67c2532a.050a0220.dc10f.0154.GAE@google.com> (raw)
In-Reply-To: <67c16ce2.050a0220.1baf.000e.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=116557b8580000
start commit: 1e15510b71c9 Merge tag 'net-6.14-rc5' of git://git.kernel...
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=136557b8580000
console output: https://syzkaller.appspot.com/x/log.txt?x=156557b8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8de9cc84d5960254
dashboard link: https://syzkaller.appspot.com/bug?extid=de1434c5355cc909b734
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11d297b8580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=119af064580000
Reported-by: syzbot+de1434c5355cc909b734@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-03-01 0:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 7:59 [syzbot] [bcachefs?] INFO: task hung in invalidate_inode_pages2_range (3) syzbot
2025-03-01 0:22 ` syzbot [this message]
2025-08-08 5:41 ` Alan Huang
2025-08-08 9:36 ` Alan Huang
2025-08-08 10:12 ` 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=67c2532a.050a0220.dc10f.0154.GAE@google.com \
--to=syzbot+de1434c5355cc909b734@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 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.