From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Linkui Xiao <xiaolinkui@126.com>, <anthony.l.nguyen@intel.com>,
<andrew+netdev@lunn.ch>, <davem@davemloft.net>,
<edumazet@google.com>, <pabeni@redhat.com>,
<intel-wired-lan@lists.osuosl.org>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Linkui Xiao <xiaolinkui@kylinos.cn>
Subject: Re: [PATCH] ixgbe: fix incomplete ACI command buffer backup on retry
Date: Mon, 14 Sep 2026 11:52:50 +0200 [thread overview]
Message-ID: <4ad84736-f0cc-4ac6-aee2-8b21a5b8b8d1@intel.com> (raw)
In-Reply-To: <20260912013403.2818191-1-xiaolinkui@126.com>
On 9/12/26 03:34, Linkui Xiao wrote:
> From: Linkui Xiao <xiaolinkui@kylinos.cn>
>
> ixgbe_aci_send_cmd() backs up the indirect command buffer so that it can
> be restored before an EBUSY retry, but the backup only copies the very
> first byte of it:
>
> buf_cpy = kmalloc(buf_size, GFP_KERNEL);
> ...
> *buf_cpy = *(u8 *)buf;
>
> while the restore path copies the full buffer back out of it:
>
> if (buf)
> memcpy(buf, buf_cpy, buf_size);
>
> So every retry hands the firmware a buffer whose content, apart from the
> first byte, is uninitialized slab memory, and on a read command the
> caller's buffer is overwritten with that garbage when the retry finally
> gives up. The buffer of a read command is an output buffer, so the caller
> does not initialize it either.
>
> Use kmemdup() to copy the whole buffer, exactly like the equivalent
> ice_sq_send_cmd() already does.
>
> Also skip the backup when buf_size is 0. kmalloc(0) returns
> ZERO_SIZE_PTR and the single byte store above would write to it, and
> restore based on buf_cpy instead of buf so that this case never passes
> ZERO_SIZE_PTR to memcpy().
>
> Fixes: 46761fd52a88 ("ixgbe: Add support for E610 FW Admin Command Interface")
> Signed-off-by: Linkui Xiao <xiaolinkui@kylinos.cn>
> ---
> drivers/net/ethernet/intel/ixgbe/ixgbe_e610.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_e610.c b/drivers/net/ethernet/intel/ixgbe/ixgbe_e610.c
> index 4d8ae5b56145..5dd88ee7ea58 100644
> --- a/drivers/net/ethernet/intel/ixgbe/ixgbe_e610.c
> +++ b/drivers/net/ethernet/intel/ixgbe/ixgbe_e610.c
> @@ -214,11 +214,10 @@ int ixgbe_aci_send_cmd(struct ixgbe_hw *hw, struct libie_aq_desc *desc,
>
> is_cmd_for_retry = ixgbe_should_retry_aci_send_cmd_execute(opcode);
> if (is_cmd_for_retry) {
> - if (buf) {
> - buf_cpy = kmalloc(buf_size, GFP_KERNEL);
> + if (buf && buf_size) {
> + buf_cpy = kmemdup(buf, buf_size, GFP_KERNEL);
> if (!buf_cpy)
> return -ENOMEM;
> - *buf_cpy = *(u8 *)buf;
> }
> desc_cpy = *desc;
> }
> @@ -234,7 +233,7 @@ int ixgbe_aci_send_cmd(struct ixgbe_hw *hw, struct libie_aq_desc *desc,
> last_status != LIBIE_AQ_RC_EBUSY)
> break;
>
> - if (buf)
> + if (buf_cpy)
ough ;F, thank your for the cleanup
Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> memcpy(buf, buf_cpy, buf_size);
> *desc = desc_cpy;
>
next prev parent reply other threads:[~2026-09-14 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 1:34 Linkui Xiao
2026-09-14 9:52 ` Przemek Kitszel [this message]
2026-09-15 15:34 ` netdev-bot+sashiko
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=4ad84736-f0cc-4ac6-aee2-8b21a5b8b8d1@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=xiaolinkui@126.com \
--cc=xiaolinkui@kylinos.cn \
/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®