From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Yunseong Kim <ysk@kzalloc.com>
Cc: Dmitry Vyukov <dvyukov@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Byungchul Park <byungchul@sk.com>,
max.byungchul.park@gmail.com, Yeoreum Yun <yeoreum.yun@arm.com>,
Michelle Jin <shjy180909@gmail.com>,
linux-kernel@vger.kernel.org,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Alan Stern <stern@rowland.harvard.edu>,
Thomas Gleixner <tglx@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
stable@vger.kernel.org, kasan-dev@googlegroups.com,
syzkaller@googlegroups.com, linux-usb@vger.kernel.org,
linux-rt-devel@lists.linux.dev
Subject: Re: [PATCH] kcov, usb: Fix invalid context sleep in softirq path on PREEMPT_RT
Date: Sat, 26 Jul 2025 08:36:37 +0200 [thread overview]
Message-ID: <2025072615-espresso-grandson-d510@gregkh> (raw)
In-Reply-To: <20250725201400.1078395-2-ysk@kzalloc.com>
On Fri, Jul 25, 2025 at 08:14:01PM +0000, Yunseong Kim wrote:
> When fuzzing USB with syzkaller on a PREEMPT_RT enabled kernel, following
> bug is triggered in the ksoftirqd context.
>
> | BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48
> | in_atomic(): 0, irqs_disabled(): 1, non_block: 0, pid: 30, name: ksoftirqd/1
> | preempt_count: 0, expected: 0
> | RCU nest depth: 2, expected: 2
> | CPU: 1 UID: 0 PID: 30 Comm: ksoftirqd/1 Tainted: G W 6.16.0-rc1-rt1 #11 PREEMPT_RT
> | Tainted: [W]=WARN
> | Hardware name: QEMU KVM Virtual Machine, BIOS 2025.02-8 05/13/2025
> | Call trace:
> | show_stack+0x2c/0x3c (C)
> | __dump_stack+0x30/0x40
> | dump_stack_lvl+0x148/0x1d8
> | dump_stack+0x1c/0x3c
> | __might_resched+0x2e4/0x52c
> | rt_spin_lock+0xa8/0x1bc
> | kcov_remote_start+0xb0/0x490
> | __usb_hcd_giveback_urb+0x2d0/0x5e8
> | usb_giveback_urb_bh+0x234/0x3c4
> | process_scheduled_works+0x678/0xd18
> | bh_worker+0x2f0/0x59c
> | workqueue_softirq_action+0x104/0x14c
> | tasklet_action+0x18/0x8c
> | handle_softirqs+0x208/0x63c
> | run_ksoftirqd+0x64/0x264
> | smpboot_thread_fn+0x4ac/0x908
> | kthread+0x5e8/0x734
> | ret_from_fork+0x10/0x20
Why is this only a USB thing? What is unique about it to trigger this
issue?
thanks,
greg k-h
next prev parent reply other threads:[~2025-07-26 6:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 20:14 [PATCH] kcov, usb: Fix invalid context sleep in softirq path on PREEMPT_RT Yunseong Kim
2025-07-26 6:36 ` Greg Kroah-Hartman [this message]
2025-07-26 7:44 ` Tetsuo Handa
2025-07-26 7:59 ` Greg Kroah-Hartman
2025-07-26 11:59 ` Thomas Gleixner
2025-08-01 22:06 ` Yunseong Kim
2025-08-08 16:33 ` Sebastian Andrzej Siewior
2025-08-08 17:35 ` Yunseong Kim
2025-08-11 8:31 ` Sebastian Andrzej Siewior
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=2025072615-espresso-grandson-d510@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andreyknvl@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=byungchul@sk.com \
--cc=dvyukov@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=linux-usb@vger.kernel.org \
--cc=max.byungchul.park@gmail.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=shjy180909@gmail.com \
--cc=stable@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=syzkaller@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=yeoreum.yun@arm.com \
--cc=ysk@kzalloc.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