From: patchwork-bot+netdevbpf@kernel.org
To: Miguel Garcia <miguelgarciaroman8@gmail.com>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, jacob.e.keller@intel.com,
syzbot+372a7d84708b07f64d9b@syzkaller.appspotmail.com,
linux-kernel@vger.kernel.org, jiri@resnulli.us,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org
Subject: Re: [PATCH net v4] devlink: use direct firmware requests for flash updates
Date: Fri, 04 Sep 2026 00:20:09 +0000 [thread overview]
Message-ID: <178848120911.4082713.2895395373266662503.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260902095739.3587287-1-miguelgarciaroman8@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 2 Sep 2026 11:57:30 +0200 you wrote:
> request_firmware() may enter the sysfs fallback and call
> try_to_freeze(). Devlink invokes it while holding the instance lock,
> causing syzbot to report:
>
> WARNING: syz-executor/... still has locks held!
>
> Firmware flash requests already name a file provided by userspace.
> Use request_firmware_direct() in both flash update paths so a missing
> file fails immediately instead of entering the sysfs fallback. This
> keeps the normal devlink locking intact.
>
> [...]
Here is the summary with links:
- [net,v4] devlink: use direct firmware requests for flash updates
https://git.kernel.org/netdev/net-next/c/94284e5442ba
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-04 0:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 9:57 [PATCH net v4] devlink: use direct firmware requests for flash updates Miguel Garcia
2026-09-04 0:20 ` 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=178848120911.4082713.2895395373266662503.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miguelgarciaroman8@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+372a7d84708b07f64d9b@syzkaller.appspotmail.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