public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+9a3c54f52bd1edbd975f@syzkaller.appspotmail.com>
To: halves@igalia.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] KASAN: slab-use-after-free Write in usb_anchor_suspend_wakeups (2)
Date: Thu, 12 Mar 2026 05:23:02 -0700	[thread overview]
Message-ID: <69b2b026.a00a0220.94e15.0024.GAE@google.com> (raw)
In-Reply-To: <DH0SAUDQWB1S.3A4ZGVEXE6PGV@igalia.com>

Hello,

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

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

Tested on:

commit:         80234b5a Merge tag 'rproc-v7.0-fixes' of git://git.ker..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11d2775a580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=5b33ceebbe3e9ed3
dashboard link: https://syzkaller.appspot.com/bug?extid=9a3c54f52bd1edbd975f
compiler:       Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1161ef5a580000

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

       reply	other threads:[~2026-03-12 12:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DH0SAUDQWB1S.3A4ZGVEXE6PGV@igalia.com>
2026-03-12 12:23 ` syzbot [this message]
     [not found] <DH0RNNST0EFG.2Z52WZH6PSBB0@igalia.com>
2026-03-12 11:52 ` [syzbot] [usb?] KASAN: slab-use-after-free Write in usb_anchor_suspend_wakeups (2) syzbot
     [not found] <48d56857-fd66-44fd-8bd1-f5af7771c1adn@googlegroups.com>
2026-03-11 21:23 ` syzbot
2024-04-01 16:50 syzbot
2024-04-01 23:01 ` Hillf Danton
2024-04-02  3:52   ` 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=69b2b026.a00a0220.94e15.0024.GAE@google.com \
    --to=syzbot+9a3c54f52bd1edbd975f@syzkaller.appspotmail.com \
    --cc=halves@igalia.com \
    --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