From: syzbot <syzbot+750f21d691e244b473b1@syzkaller.appspotmail.com>
To: dhowells@redhat.com, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org, marc.dionne@auristor.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [afs?] INFO: task hung in afs_cell_purge (2)
Date: Sat, 07 Jun 2025 15:45:04 -0700 [thread overview]
Message-ID: <6844c0f0.a70a0220.27c366.004a.GAE@google.com> (raw)
In-Reply-To: <68185b7b.a70a0220.254cdc.0046.GAE@google.com>
syzbot has bisected this issue to:
commit 1d0b929fc070b4115403a0a6206a0c6a62dd61f5
Author: David Howells <dhowells@redhat.com>
Date: Mon Feb 24 09:52:58 2025 +0000
afs: Change dynroot to create contents on demand
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1522020c580000
start commit: 7a13c14ee59d Merge tag 'for-6.15-rc4-tag' of git://git.ker..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1722020c580000
console output: https://syzkaller.appspot.com/x/log.txt?x=1322020c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a42a9d552788177b
dashboard link: https://syzkaller.appspot.com/bug?extid=750f21d691e244b473b1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13a101cc580000
Reported-by: syzbot+750f21d691e244b473b1@syzkaller.appspotmail.com
Fixes: 1d0b929fc070 ("afs: Change dynroot to create contents on demand")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-06-07 22:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 6:32 [syzbot] [afs?] INFO: task hung in afs_cell_purge (2) syzbot
2025-06-07 22:45 ` syzbot [this message]
2025-07-21 14:02 ` David Howells
2025-07-21 15:41 ` Aleksandr Nogikh
[not found] <20250608054619.924-1-hdanton@sina.com>
2025-06-08 6:13 ` 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=6844c0f0.a70a0220.27c366.004a.GAE@google.com \
--to=syzbot+750f21d691e244b473b1@syzkaller.appspotmail.com \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).