From: syzbot <syzbot+1de5a37cb85a2d536330@syzkaller.appspotmail.com>
To: linkinjeon@kernel.org, linux-integrity@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, sj1557.seo@samsung.com,
syzkaller-bugs@googlegroups.com, yuezhang.mo@sony.com
Subject: Re: [syzbot] [integrity?] [lsm?] INFO: task hung in process_measurement (2)
Date: Sun, 15 Dec 2024 22:31:02 -0800 [thread overview]
Message-ID: <675fc926.050a0220.37aaf.0116.GAE@google.com> (raw)
In-Reply-To: <PUZPR04MB6316F684BF023564B7DDD812813B2@PUZPR04MB6316.apcprd04.prod.outlook.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+1de5a37cb85a2d536330@syzkaller.appspotmail.com
Tested-by: syzbot+1de5a37cb85a2d536330@syzkaller.appspotmail.com
Tested on:
commit: 78d4f34e Linux 6.13-rc3
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11259ed7980000
kernel config: https://syzkaller.appspot.com/x/.config?x=6fe704d2356374ad
dashboard link: https://syzkaller.appspot.com/bug?extid=1de5a37cb85a2d536330
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=105d1730580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-12-16 6:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 8:36 [syzbot] [integrity?] [lsm?] INFO: task hung in process_measurement (2) syzbot
2024-12-07 19:18 ` syzbot
2024-12-09 15:02 ` syzbot
2024-12-10 10:06 ` Yuezhang.Mo
2024-12-10 10:35 ` syzbot
2024-12-11 2:15 ` Yuezhang.Mo
2024-12-11 3:14 ` syzbot
2024-12-16 6:04 ` Yuezhang.Mo
2024-12-16 6:31 ` syzbot [this message]
2024-12-30 5:14 ` Yuezhang.Mo
2024-12-30 5:48 ` 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=675fc926.050a0220.37aaf.0116.GAE@google.com \
--to=syzbot+1de5a37cb85a2d536330@syzkaller.appspotmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sj1557.seo@samsung.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yuezhang.mo@sony.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).