public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+01218003be74b5e1213a@syzkaller.appspotmail.com>
To: linkinjeon@kernel.org, linux-fsdevel@vger.kernel.org,
	 linux-kernel@vger.kernel.org, sj1557.seo@samsung.com,
	 syzkaller-bugs@googlegroups.com, yuezhang.mo@sony.com
Subject: Re: [syzbot] [exfat?] KMSAN: uninit-value in __exfat_get_dentry_set
Date: Wed, 16 Oct 2024 19:57:03 -0700	[thread overview]
Message-ID: <67107cff.050a0220.d5849.001d.GAE@google.com> (raw)
In-Reply-To: <PUZPR04MB631653574B414EF831C1FEDC81472@PUZPR04MB6316.apcprd04.prod.outlook.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+01218003be74b5e1213a@syzkaller.appspotmail.com
Tested-by: syzbot+01218003be74b5e1213a@syzkaller.appspotmail.com

Tested on:

commit:         c964ced7 Merge tag 'for-linus' of git://git.kernel.org..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12c43030580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=5242e0e980477c72
dashboard link: https://syzkaller.appspot.com/bug?extid=01218003be74b5e1213a
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1738345f980000

Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2024-10-17  2:57 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-05 14:32 [syzbot] [exfat?] KMSAN: uninit-value in __exfat_get_dentry_set syzbot
2024-10-10 12:39 ` [syzbot] " syzbot
2024-10-10 14:01 ` syzbot
2024-10-11 12:33 ` syzbot
2024-10-11 13:04 ` syzbot
2024-10-12  7:48 ` [syzbot] Re: [syzbot] [exfat?] " syzbot
2024-10-12 15:38 ` Suraj Sonawane
2024-10-12 18:23   ` syzbot
2024-10-14  6:39 ` Yuezhang.Mo
2024-10-14  7:51   ` syzbot
2024-10-14  9:00 ` Yuezhang.Mo
2024-10-14 10:33   ` syzbot
2024-10-17  2:20 ` Yuezhang.Mo
2024-10-17  2:57   ` syzbot [this message]
2024-10-17  3:32     ` Yuezhang.Mo
2024-10-17  4:18       ` syzbot
2024-10-17  9:49 ` Yuezhang.Mo
2024-10-17 10:11   ` syzbot
2024-10-19  4:01 ` Namjae Jeon
2024-10-19  5:20   ` syzbot
2024-10-29  4:17 ` Namjae Jeon
2024-10-29  9:28   ` syzbot
     [not found] <234e554c-a93a-4a88-9d4f-6773cfc5057f@gmail.com>
2024-10-10 13:52 ` syzbot
     [not found] <96341c70-45e4-489d-9dd4-6f3171d26cab@gmail.com>
2024-10-10 14:40 ` syzbot
     [not found] <CAN=OONyV0hn1DPJLZ1sSgy3X4_vV2FcOjeUX-TgN7e-gh6=pjQ@mail.gmail.com>
2024-10-11 12:41 ` syzbot
     [not found] <CAN=OONy0dd0TK0TKJ7J-zWvZWfNPr6re9dP=WThbU-VDT-J3+g@mail.gmail.com>
2024-10-11 13:28 ` syzbot
     [not found] <CAHiZj8jjsotVt8gShhM3K+Bq0ytXXx89zFzrjjB+RGZXe_zEeQ@mail.gmail.com>
2024-10-12  8:11 ` 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=67107cff.050a0220.d5849.001d.GAE@google.com \
    --to=syzbot+01218003be74b5e1213a@syzkaller.appspotmail.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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