public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+7a4842f0b1801230a989@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	 zhaomengmeng@kylinos.cn
Subject: Re: [syzbot] [udf?] KASAN: slab-out-of-bounds Read in udf_get_filelongad (2)
Date: Wed, 11 Sep 2024 03:05:01 -0700	[thread overview]
Message-ID: <00000000000095c6290621d51f6f@google.com> (raw)
In-Reply-To: <0d2576ae-f3c9-4700-8cdb-8957944093e6@kylinos.cn>

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:         8d8d276b Merge tag 'trace-v6.11-rc6' of git://git.kern..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12416100580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=61d235cb8d15001c
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=10de7f29980000

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

       reply	other threads:[~2024-09-11 10:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0d2576ae-f3c9-4700-8cdb-8957944093e6@kylinos.cn>
2024-09-11 10:05 ` syzbot [this message]
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
2024-09-30 23:50 ` Zhao Mengmeng
2024-10-01  0:18   ` 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=00000000000095c6290621d51f6f@google.com \
    --to=syzbot+7a4842f0b1801230a989@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=zhaomengmeng@kylinos.cn \
    /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