public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+943d34fa3cf2191e3068@syzkaller.appspotmail.com>
To: Jason@zx2c4.com, davem@davemloft.net, edumazet@google.com,
	 gregkh@linuxfoundation.org, hdanton@sina.com, jason@zx2c4.com,
	 kuba@kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org,  oneukum@suse.com, pabeni@redhat.com,
	stern@rowland.harvard.edu,  syzkaller-bugs@googlegroups.com,
	tglx@linutronix.de, tj@kernel.org,  wireguard@lists.zx2c4.com
Subject: Re: [syzbot] [wireguard?] WARNING in kthread_unpark (2)
Date: Sun, 11 Aug 2024 21:53:02 -0700	[thread overview]
Message-ID: <00000000000099eca4061f754420@google.com> (raw)
In-Reply-To: <00000000000061c0a106183499ec@google.com>

syzbot has bisected this issue to:

commit b3e40fc85735b787ce65909619fcd173107113c2
Author: Oliver Neukum <oneukum@suse.com>
Date:   Thu May 2 11:51:40 2024 +0000

    USB: usb_parse_endpoint: ignore reserved bits

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=11ca267d980000
start commit:   dc1c8034e31b minmax: simplify min()/max()/clamp() implemen..
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=13ca267d980000
console output: https://syzkaller.appspot.com/x/log.txt?x=15ca267d980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=2258b49cd9b339fa
dashboard link: https://syzkaller.appspot.com/bug?extid=943d34fa3cf2191e3068
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1022b573980000

Reported-by: syzbot+943d34fa3cf2191e3068@syzkaller.appspotmail.com
Fixes: b3e40fc85735 ("USB: usb_parse_endpoint: ignore reserved bits")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2024-08-12  4:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-11 21:47 [syzbot] [wireguard?] WARNING in kthread_unpark (2) syzbot
2024-07-29 15:48 ` syzbot
2024-07-30 10:22   ` Hillf Danton
2024-07-30 11:00     ` syzbot
2024-07-30 11:30   ` Hillf Danton
2024-07-31 11:05   ` Hillf Danton
2024-07-31 11:29     ` syzbot
2024-09-11 12:04       ` [PATCH] kthread: Unpark only parked kthreads (was Re: [syzbot] [wireguard?] WARNING in kthread_unpark (2)) Frederic Weisbecker
2024-09-12 11:30         ` Hillf Danton
2024-09-12 14:26           ` [syzbot] [wireguard?] WARNING in kthread_unpark (2) syzbot
2024-09-13 12:11         ` [PATCH] kthread: Unpark only parked kthreads (was Re: [syzbot] [wireguard?] WARNING in kthread_unpark (2)) Hillf Danton
2024-09-13 12:31           ` Frederic Weisbecker
2024-09-13 12:48             ` Hillf Danton
2024-09-13 12:38           ` [syzbot] [wireguard?] WARNING in kthread_unpark (2) syzbot
2024-09-13 13:16             ` Frederic Weisbecker
2024-08-12  4:53 ` syzbot [this message]

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=00000000000099eca4061f754420@google.com \
    --to=syzbot+943d34fa3cf2191e3068@syzkaller.appspotmail.com \
    --cc=Jason@zx2c4.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdanton@sina.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=pabeni@redhat.com \
    --cc=stern@rowland.harvard.edu \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=wireguard@lists.zx2c4.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