All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+27fe438b6370f95de4a5@syzkaller.appspotmail.com>
To: dmantipov@yandex.ru, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] KMSAN: kernel-usb-infoleak-after-free in usb_start_wait_urb
Date: Tue, 08 Jul 2025 00:48:02 -0700	[thread overview]
Message-ID: <686ccd32.a00a0220.338033.0006.GAE@google.com> (raw)
In-Reply-To: <18b04472-4443-43eb-8452-56b9a31df378@yandex.ru>

Hello,

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

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

Tested on:

commit:         d7b8f8e2 Linux 6.16-rc5
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=13a15582580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=8fe1009b62db3e6e
dashboard link: https://syzkaller.appspot.com/bug?extid=27fe438b6370f95de4a5
compiler:       Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1090f28c580000

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

       reply	other threads:[~2025-07-08  7:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <18b04472-4443-43eb-8452-56b9a31df378@yandex.ru>
2025-07-08  7:48 ` syzbot [this message]
2025-07-05 16:22 [syzbot] [usb?] KMSAN: kernel-usb-infoleak-after-free in usb_start_wait_urb syzbot
2025-07-05 19:13 ` 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=686ccd32.a00a0220.338033.0006.GAE@google.com \
    --to=syzbot+27fe438b6370f95de4a5@syzkaller.appspotmail.com \
    --cc=dmantipov@yandex.ru \
    --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 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.