From: syzbot <syzbot+3e9cb93e3c5f90d28e19@syzkaller.appspotmail.com>
To: ekffu200098@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [exfat?] general protection fault in exfat_utf16_to_nls
Date: Thu, 25 Sep 2025 08:24:02 -0700 [thread overview]
Message-ID: <68d55e92.a00a0220.303701.0015.GAE@google.com> (raw)
In-Reply-To: <CABFDxMH6UKpBs8GEhvuA=E2=QDRJehK4Gzg0WbbZfYmta7Swxg@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+3e9cb93e3c5f90d28e19@syzkaller.appspotmail.com
Tested-by: syzbot+3e9cb93e3c5f90d28e19@syzkaller.appspotmail.com
Tested on:
commit: b5a4da2c Add linux-next specific files for 20250924
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15ea1d34580000
kernel config: https://syzkaller.appspot.com/x/.config?x=fc64d939cce41d2
dashboard link: https://syzkaller.appspot.com/bug?extid=3e9cb93e3c5f90d28e19
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=1105e142580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-09-25 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABFDxMH6UKpBs8GEhvuA=E2=QDRJehK4Gzg0WbbZfYmta7Swxg@mail.gmail.com>
2025-09-25 15:24 ` syzbot [this message]
[not found] <CABFDxMEZq1yjunCgJegUw5ky5GWNBw+pmSOwkfismXymJn_riw@mail.gmail.com>
2025-09-26 13:18 ` [syzbot] [exfat?] general protection fault in exfat_utf16_to_nls syzbot
[not found] <CABFDxMGo8YMhTyQcPRb64u8Mxhvug986qAVpnvf=Pe-xVeHRUw@mail.gmail.com>
2025-09-25 18:29 ` syzbot
[not found] <CABFDxMFiDMVJLdXsYb90czLsvBJJebJoK1OcZVHUHW_X9naZaQ@mail.gmail.com>
2025-09-25 14:11 ` syzbot
[not found] <CABFDxMEvAdSyAPhyNo0YWWwA7C4=KFm2qKS9DS7ExPwFvDLjDA@mail.gmail.com>
2025-09-25 4:36 ` syzbot
2025-09-24 22:04 syzbot
2025-09-25 18: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=68d55e92.a00a0220.303701.0015.GAE@google.com \
--to=syzbot+3e9cb93e3c5f90d28e19@syzkaller.appspotmail.com \
--cc=ekffu200098@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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