All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+98cc76a76de46b3714d4@syzkaller.appspotmail.com>
To: aha310510@gmail.com, ethan.ferguson@zetier.com,
	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?] KASAN: stack-out-of-bounds Read in exfat_nls_to_utf16
Date: Sun, 05 Oct 2025 21:31:01 -0700	[thread overview]
Message-ID: <68e34605.a00a0220.2ba410.0021.GAE@google.com> (raw)
In-Reply-To: <68e2ff90.050a0220.2c17c1.0039.GAE@google.com>

syzbot has bisected this issue to:

commit d01579d590f72d2d91405b708e96f6169f24775a
Author: Ethan Ferguson <ethan.ferguson@zetier.com>
Date:   Tue Sep 30 04:49:00 2025 +0000

    exfat: Add support for FS_IOC_{GET,SET}FSLABEL

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=12933334580000
start commit:   6093a688a07d Merge tag 'char-misc-6.18-rc1' of git://git.k..
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=11933334580000
console output: https://syzkaller.appspot.com/x/log.txt?x=16933334580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=e2b03b8b7809165e
dashboard link: https://syzkaller.appspot.com/bug?extid=98cc76a76de46b3714d4
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=161a3334580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13827942580000

Reported-by: syzbot+98cc76a76de46b3714d4@syzkaller.appspotmail.com
Fixes: d01579d590f7 ("exfat: Add support for FS_IOC_{GET,SET}FSLABEL")

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

      parent reply	other threads:[~2025-10-06  4:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-05 23:30 [syzbot] [exfat?] KASAN: stack-out-of-bounds Read in exfat_nls_to_utf16 syzbot
2025-10-06  3:25 ` Jeongjun Park
2025-10-06  4:11   ` syzbot
2025-10-06  4:31 ` 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=68e34605.a00a0220.2ba410.0021.GAE@google.com \
    --to=syzbot+98cc76a76de46b3714d4@syzkaller.appspotmail.com \
    --cc=aha310510@gmail.com \
    --cc=ethan.ferguson@zetier.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.