From: syzbot <syzbot+cb9e66807bcb882cd0c5@syzkaller.appspotmail.com>
To: bfoster@redhat.com, dmitry.kasatkin@gmail.com,
eric.snowberg@oracle.com, jmorris@namei.org,
kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, paul@paul-moore.com,
roberto.sassu@huawei.com, serge@hallyn.com,
syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org,
zohar@linux.ibm.com
Subject: Re: [syzbot] [lsm?] [integrity?] INFO: task hung in process_measurement (3)
Date: Sat, 27 Dec 2025 22:29:01 -0800 [thread overview]
Message-ID: <6950ce2d.a70a0220.c527.0006.GAE@google.com> (raw)
In-Reply-To: <682e11b1.050a0220.ade60.09e5.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=10499e2a580000
start commit: 172a9d94339c Merge tag '6.15-rc6-smb3-client-fixes' of git..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=ea35e429f965296e
dashboard link: https://syzkaller.appspot.com/bug?extid=cb9e66807bcb882cd0c5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16836e70580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1617a2d4580000
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
prev parent reply other threads:[~2025-12-28 6:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 17:47 [syzbot] [integrity?] [lsm?] INFO: task hung in process_measurement (3) syzbot
2025-12-28 6:29 ` syzbot [this message]
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=6950ce2d.a70a0220.c527.0006.GAE@google.com \
--to=syzbot+cb9e66807bcb882cd0c5@syzkaller.appspotmail.com \
--cc=bfoster@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=eric.snowberg@oracle.com \
--cc=jmorris@namei.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=roberto.sassu@huawei.com \
--cc=serge@hallyn.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=zohar@linux.ibm.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).