From: syzbot <syzbot+30c83da54e948f6e9436@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
xandfury@gmail.com
Subject: Re: [syzbot] [v9fs?] UBSAN: shift-out-of-bounds in v9fs_get_tree
Date: Sun, 28 Sep 2025 13:44:01 -0700 [thread overview]
Message-ID: <68d99e11.a00a0220.102ee.0031.GAE@google.com> (raw)
In-Reply-To: <87h5wm2ybu.fsf@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+30c83da54e948f6e9436@syzkaller.appspotmail.com
Tested-by: syzbot+30c83da54e948f6e9436@syzkaller.appspotmail.com
Tested on:
commit: 26285807 Add linux-next specific files for 20250926
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15090334580000
kernel config: https://syzkaller.appspot.com/x/.config?x=997066872b7941b6
dashboard link: https://syzkaller.appspot.com/bug?extid=30c83da54e948f6e9436
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-09-28 20:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87h5wm2ybu.fsf@gmail.com>
2025-09-28 20:44 ` syzbot [this message]
[not found] <87ikh32pm3.fsf@gmail.com>
2025-09-28 4:45 ` [syzbot] [v9fs?] UBSAN: shift-out-of-bounds in v9fs_get_tree syzbot
2025-08-21 2:58 syzbot
2025-08-21 3:48 ` Dominique Martinet
2025-08-21 4:06 ` syzbot
2025-09-24 23:14 ` Eric Sandeen
2025-08-21 8:47 ` Hillf Danton
2025-08-21 9:23 ` syzbot
2025-08-22 13:31 ` Yuichiro Tsuji
2025-08-22 14:56 ` syzbot
2025-08-22 13:45 ` Yuichiro Tsuji
2025-08-22 17:47 ` syzbot
2025-08-22 14:27 ` Edward Adam Davis
2025-08-22 18:05 ` 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=68d99e11.a00a0220.102ee.0031.GAE@google.com \
--to=syzbot+30c83da54e948f6e9436@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xandfury@gmail.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.