All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+9a4aec827829942045ff@syzkaller.appspotmail.com>
To: dmantipov@yandex.ru, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] stack segment fault in __usb_hcd_giveback_urb
Date: Mon, 16 Jun 2025 11:10:05 -0700	[thread overview]
Message-ID: <68505dfd.050a0220.2608ac.0008.GAE@google.com> (raw)
In-Reply-To: <d8f04f74-283e-4acf-9e42-94fc0a047228@yandex.ru>

Hello,

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

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

Tested on:

commit:         44a5ab7a Merge tag 'powerpc-6.16-3' of git://git.kerne..
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=11a48370580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=8f72e140c622500d
dashboard link: https://syzkaller.appspot.com/bug?extid=9a4aec827829942045ff
compiler:       Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
patch:          https://syzkaller.appspot.com/x/patch.diff?x=175515d4580000

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

       reply	other threads:[~2025-06-16 18:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d8f04f74-283e-4acf-9e42-94fc0a047228@yandex.ru>
2025-06-16 18:10 ` syzbot [this message]
     [not found] <e648f349-6bad-44fb-a5f6-5a72a4cc2953@yandex.ru>
2025-06-10  9:57 ` [syzbot] [usb?] stack segment fault in __usb_hcd_giveback_urb syzbot
     [not found] <20250607084517.897-1-hdanton@sina.com>
2025-06-07  9:19 ` syzbot
     [not found] <20250607074300.873-1-hdanton@sina.com>
2025-06-07  8:19 ` syzbot
2025-06-07  1:16 syzbot
2025-07-20  5:40 ` 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=68505dfd.050a0220.2608ac.0008.GAE@google.com \
    --to=syzbot+9a4aec827829942045ff@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.