From: Jakub Kicinski <kuba@kernel.org>
To: qianjiaru77@gmail.com
Cc: michael.chan@broadcom.com, pavan.chebbi@broadcom.com,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
andrew+netdev@lunn.ch, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] VF Resource State Inconsistency Vulnerability in Linux bnxt_en Driver
Date: Fri, 29 Aug 2025 19:02:44 -0700 [thread overview]
Message-ID: <20250829190244.348ce433@kernel.org> (raw)
In-Reply-To: <20250827135102.5923-1-qianjiaru77@gmail.com>
On Wed, 27 Aug 2025 21:51:02 +0800 qianjiaru77@gmail.com wrote:
> Subject: [PATCH v2 1/1] VF Resource State Inconsistency Vulnerability in Linux bnxt_en Driver
Please look at the git history to find out what the normal subject
format is. Something like:
eth: bnxt: fix VF resource inconsistency with old FW API
is probably a good choice.
> From: qianjiaru <qianjiaru77@gmail.com>
>
> A state management vulnerability exists in the
> `bnxt_hwrm_reserve_vf_rings()` function of the Linux kernel's
> bnxt_en network driver. The vulnerability causes incomplete
> resource state updates in SR-IOV Virtual Function (VF) environments,
> potentially leading to system instability and resource allocation
> failures in virtualized deployments.
Please *succinctly* explain what the bug is, assuming the person
reading the description can also read the code. Or should I say
ask your LLM to do it, 'cause I really doubt you wrote this bloviated
slop.
> Signed-off-by: qianjiaru <qianjiaru77@gmail.com>
You must provide an appropriate Fixes tag for fixes in the Linux kernel.
--
pw-bot: cr
prev parent reply other threads:[~2025-08-30 2:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 13:51 qianjiaru77
2025-08-30 2:02 ` Jakub Kicinski [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=20250829190244.348ce433@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=qianjiaru77@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®