mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+abd6a8dca0f2b7726060@syzkaller.appspotmail.com>
To: jchuang26@m.fudan.edu.cn, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] UBSAN: shift-out-of-bounds in null_process_zoned_cmd
Date: Sun, 13 Sep 2026 22:21:04 -0700	[thread overview]
Message-ID: <6aa78440.f81106d8.2ab401.003d.GAE@google.com> (raw)
In-Reply-To: <6aa780ed.9c80204b.1abe44.649aSMTPIN_ADDED_BROKEN@gmr-mx.google.com>

Hello,

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

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

Tested on:

commit:         069f4aad Merge tag 'md-7.3-20260809' of https://git.ke..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=15cf35f9580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=acc0a882b963ae23
dashboard link: https://syzkaller.appspot.com/bug?extid=abd6a8dca0f2b7726060
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.

       reply	other threads:[~2026-09-14  5:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6aa780ed.9c80204b.1abe44.649aSMTPIN_ADDED_BROKEN@gmr-mx.google.com>
2026-09-14  5:21 ` syzbot [this message]
     [not found] <6aa7763f.8ff42d3a.a6660.e668SMTPIN_ADDED_BROKEN@gmr-mx.google.com>
2026-09-14  4:47 ` syzbot
     [not found] <6aa775d6.2e7c7dfd.df720.5565SMTPIN_ADDED_BROKEN@gmr-mx.google.com>
2026-09-14  4:33 ` syzbot
2026-08-06 15:37 syzbot
2026-08-13 12:10 ` syzbot
2026-08-14 11:44   ` Niklas Cassel

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=6aa78440.f81106d8.2ab401.003d.GAE@google.com \
    --to=syzbot+abd6a8dca0f2b7726060@syzkaller.appspotmail.com \
    --cc=jchuang26@m.fudan.edu.cn \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®