All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+8d6fbb27a6aded64b25b@syzkaller.appspotmail.com>
To: 18801353760@163.com, almaz.alexandrovich@paragon-software.com,
	 linux-kernel@vger.kernel.org, ntfs3@lists.linux.dev,
	 syzkaller-bugs@googlegroups.com, yin31149@gmail.com
Subject: Re: [syzbot] KASAN: slab-out-of-bounds Read in run_unpack
Date: Thu, 22 Sep 2022 20:37:20 -0700	[thread overview]
Message-ID: <0000000000002d50a505e94fe5bd@google.com> (raw)
In-Reply-To: <20220923031722.3744-1-yin31149@gmail.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+8d6fbb27a6aded64b25b@syzkaller.appspotmail.com

Tested on:

commit:         bf682942 Merge tag 'scsi-fixes' of git://git.kernel.or..
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=15dcd888880000
kernel config:  https://syzkaller.appspot.com/x/.config?x=122d7bd4fc8e0ecb
dashboard link: https://syzkaller.appspot.com/bug?extid=8d6fbb27a6aded64b25b
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1476e5b0880000

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

  reply	other threads:[~2022-09-23  3:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 22:46 [syzbot] KASAN: slab-out-of-bounds Read in run_unpack syzbot
2022-09-23  3:17 ` Hawkins Jiawei
2022-09-23  3:37   ` syzbot [this message]
2022-09-23  8:49     ` [PATCH] fs/ntfs3: fix " Hawkins Jiawei
2022-09-23 10:27       ` Hawkins Jiawei
2022-09-23 10:45         ` [syzbot] KASAN: " syzbot
2022-09-23 11:09 ` [PATCH v2] fs/ntfs3: fix " Hawkins Jiawei
2022-09-30 16:09   ` Konstantin Komarov

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=0000000000002d50a505e94fe5bd@google.com \
    --to=syzbot+8d6fbb27a6aded64b25b@syzkaller.appspotmail.com \
    --cc=18801353760@163.com \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ntfs3@lists.linux.dev \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=yin31149@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.