From: syzbot <syzbot+7a4842f0b1801230a989@syzkaller.appspotmail.com>
To: jack@suse.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, zhaomengmeng@kylinos.cn,
zhaomzhao@126.com
Subject: Re: [syzbot] [udf?] KASAN: slab-out-of-bounds Read in udf_get_filelongad (2)
Date: Thu, 26 Sep 2024 05:03:03 -0700 [thread overview]
Message-ID: <66f54d77.050a0220.211276.006d.GAE@google.com> (raw)
In-Reply-To: <29447f93-7b01-499c-85c2-747285d0a73c@126.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+7a4842f0b1801230a989@syzkaller.appspotmail.com
Tested-by: syzbot+7a4842f0b1801230a989@syzkaller.appspotmail.com
Tested on:
commit: 67784a74 Merge tag 'ata-6.11-rc7' of git://git.kernel...
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=1125b627980000
kernel config: https://syzkaller.appspot.com/x/.config?x=660f6eb11f9c7dc5
dashboard link: https://syzkaller.appspot.com/bug?extid=7a4842f0b1801230a989
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=1459b627980000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-09-26 12:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 9:55 [syzbot] [udf?] KASAN: slab-out-of-bounds Read in udf_get_filelongad (2) syzbot
2024-09-10 7:28 ` Zhao Mengmeng
2024-09-10 7:43 ` syzbot
2024-09-18 8:53 ` Zhao Mengmeng
2024-09-18 9:15 ` syzbot
2024-09-26 11:36 ` Zhao Mengmeng
2024-09-26 12:03 ` syzbot [this message]
2024-09-11 9:44 ` [syzbot] " syzbot
2024-09-30 23:50 ` Zhao Mengmeng
2024-10-01 0:18 ` syzbot
[not found] <0d2576ae-f3c9-4700-8cdb-8957944093e6@kylinos.cn>
2024-09-11 10: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=66f54d77.050a0220.211276.006d.GAE@google.com \
--to=syzbot+7a4842f0b1801230a989@syzkaller.appspotmail.com \
--cc=jack@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=zhaomengmeng@kylinos.cn \
--cc=zhaomzhao@126.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.