The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: syzbot <syzbot+6af973a3b8dfd2faefdc@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] BUG: unable to handle kernel NULL pointer dereference in lo_rw_aio
Date: Thu, 24 Apr 2025 22:13:02 -0700	[thread overview]
Message-ID: <680b19de.050a0220.2c0118.0c74.GAE@google.com> (raw)
In-Reply-To: <20250425045419.3440264-1-lizhi.xu@windriver.com>

Hello,

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

Reported-by: syzbot+6af973a3b8dfd2faefdc@syzkaller.appspotmail.com
Tested-by: syzbot+6af973a3b8dfd2faefdc@syzkaller.appspotmail.com

Tested on:

commit:         02ddfb98 Merge tag 'scsi-fixes' of git://git.kernel.or..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15b3fd9b980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=efa83f9a6dd67d67
dashboard link: https://syzkaller.appspot.com/bug?extid=6af973a3b8dfd2faefdc
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=13467fcf980000

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

       reply	other threads:[~2025-04-25  5:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250425045419.3440264-1-lizhi.xu@windriver.com>
2025-04-25  5:13 ` syzbot [this message]
     [not found] <20250425015516.3126195-1-lizhi.xu@windriver.com>
2025-04-25  2:14 ` [syzbot] [block?] BUG: unable to handle kernel NULL pointer dereference in lo_rw_aio syzbot
     [not found] <20250425011940.3072994-1-lizhi.xu@windriver.com>
2025-04-25  1:33 ` syzbot
2025-04-24 14:08 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=680b19de.050a0220.2c0118.0c74.GAE@google.com \
    --to=syzbot+6af973a3b8dfd2faefdc@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizhi.xu@windriver.com \
    --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