From: patchwork-bot+netdevbpf@kernel.org
To: Matvey Valigura <valigurasm@gmail.com>
Cc: gregkh@linuxfoundation.org, 3chas3@gmail.com,
duncan.sands@free.fr, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzbot+9ca2c9f85bd8b5e46516@syzkaller.appspotmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH] usb: atm: use request_firmware_direct() for firmware probing
Date: Tue, 29 Sep 2026 23:50:07 +0000 [thread overview]
Message-ID: <179072580753.1169866.12044189359267660382.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260924050654.15347-1-valigurasm@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 24 Sep 2026 08:06:54 +0300 you wrote:
> When disconnecting a device while firmware is not present on the system,
> usbatm_usb_disconnect() waits for the heavy_init thread to finish:
> wait_for_completion(&instance->thread_exited);
>
> If CONFIG_FW_LOADER_USER_HELPER_FALLBACK is enabled, missing firmware
> causes request_firmware() to fall back to sysfs/udevd. This creates a
> circular dependency during disconnect:
> 1. usb_disconnect() holds device_lock(&udev->dev).
> 2. usbatm_usb_disconnect() waits for instance->thread to exit.
> 3. instance->thread waits for request_firmware() sysfs fallback.
> 4. udevd receives the firmware uevent and attempts to read sysfs
> attributes (e.g. serial), blocking on device_lock(&udev->dev).
>
> [...]
Here is the summary with links:
- usb: atm: use request_firmware_direct() for firmware probing
https://git.kernel.org/netdev/net-next/c/f10883b37d9c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-29 23:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 5:06 Matvey Valigura
2026-09-29 14:27 ` Simon Horman
2026-09-29 23:50 ` patchwork-bot+netdevbpf [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=179072580753.1169866.12044189359267660382.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=3chas3@gmail.com \
--cc=duncan.sands@free.fr \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+9ca2c9f85bd8b5e46516@syzkaller.appspotmail.com \
--cc=valigurasm@gmail.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
all inboxes | Powered by JetHome®