public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+1de5a37cb85a2d536330@syzkaller.appspotmail.com>
To: Yuezhang.Mo@sony.com, andy.wu@sony.com, bp@alien8.de,
	 dave.hansen@linux.intel.com, dmitry.kasatkin@gmail.com,
	 eric.snowberg@oracle.com, hpa@zytor.com, jmorris@namei.org,
	 linkinjeon@kernel.org, linux-integrity@vger.kernel.org,
	 linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org,  mingo@redhat.com,
	paul@paul-moore.com, roberto.sassu@huawei.com,  serge@hallyn.com,
	sj1557.seo@samsung.com, syzkaller-bugs@googlegroups.com,
	 tglx@linutronix.de, wataru.aoyama@sony.com, x86@kernel.org,
	 yuezhang.mo@sony.com, zohar@linux.ibm.com
Subject: Re: [syzbot] [integrity?] [lsm?] INFO: task hung in process_measurement (2)
Date: Mon, 09 Dec 2024 07:02:03 -0800	[thread overview]
Message-ID: <6757066b.050a0220.a30f1.01a5.GAE@google.com> (raw)
In-Reply-To: <00000000000065deef0604e8fe03@google.com>

syzbot has bisected this issue to:

commit f55c096f62f100aa9f5f48d86e1b6846ecbd67e7
Author: Yuezhang Mo <Yuezhang.Mo@sony.com>
Date:   Tue May 30 09:35:00 2023 +0000

    exfat: do not zero the extended part

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=15275944580000
start commit:   b5f217084ab3 Merge tag 'bpf-fixes' of git://git.kernel.org..
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=17275944580000
console output: https://syzkaller.appspot.com/x/log.txt?x=13275944580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=335e39020523e2ed
dashboard link: https://syzkaller.appspot.com/bug?extid=1de5a37cb85a2d536330
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=126a8820580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=153e70f8580000

Reported-by: syzbot+1de5a37cb85a2d536330@syzkaller.appspotmail.com
Fixes: f55c096f62f1 ("exfat: do not zero the extended part")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  parent reply	other threads:[~2024-12-09 15:02 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 [this message]
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
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=6757066b.050a0220.a30f1.01a5.GAE@google.com \
    --to=syzbot+1de5a37cb85a2d536330@syzkaller.appspotmail.com \
    --cc=Yuezhang.Mo@sony.com \
    --cc=andy.wu@sony.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=eric.snowberg@oracle.com \
    --cc=hpa@zytor.com \
    --cc=jmorris@namei.org \
    --cc=linkinjeon@kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paul@paul-moore.com \
    --cc=roberto.sassu@huawei.com \
    --cc=serge@hallyn.com \
    --cc=sj1557.seo@samsung.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=wataru.aoyama@sony.com \
    --cc=x86@kernel.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