From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Piotr Kwapulinski <piotr.kwapulinski@intel.com>
Cc: <intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
<dan.carpenter@linaro.org>, <yuehaibing@huawei.com>,
<przemyslaw.kitszel@intel.com>
Subject: Re: [PATCH iwl-next v2] ixgbe: Fix possible skb NULL pointer dereference
Date: Mon, 20 Jan 2025 15:45:19 +0100 [thread overview]
Message-ID: <Z45hfyEC6dE2Zkm3@boxer> (raw)
In-Reply-To: <20250117154935.9444-1-piotr.kwapulinski@intel.com>
On Fri, Jan 17, 2025 at 04:49:35PM +0100, Piotr Kwapulinski wrote:
> The commit c824125cbb18 ("ixgbe: Fix passing 0 to ERR_PTR in
> ixgbe_run_xdp()") stopped utilizing the ERR-like macros for xdp status
> encoding. Propagate this logic to the ixgbe_put_rx_buffer().
>
> The commit also relaxed the skb NULL pointer check - caught by Smatch.
> Restore this check.
>
> Fixes: c824125cbb18 ("ixgbe: Fix passing 0 to ERR_PTR in ixgbe_run_xdp()")
> Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
> Signed-off-by: Piotr Kwapulinski <piotr.kwapulinski@intel.com>
> ---
> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c b/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
> index 7236f20..c682c3d 100644
> --- a/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
> +++ b/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
> @@ -2098,14 +2098,14 @@ static struct ixgbe_rx_buffer *ixgbe_get_rx_buffer(struct ixgbe_ring *rx_ring,
>
> static void ixgbe_put_rx_buffer(struct ixgbe_ring *rx_ring,
> struct ixgbe_rx_buffer *rx_buffer,
> - struct sk_buff *skb,
> - int rx_buffer_pgcnt)
> + struct sk_buff *skb, int rx_buffer_pgcnt,
> + int xdp_res)
> {
> if (ixgbe_can_reuse_rx_page(rx_buffer, rx_buffer_pgcnt)) {
> /* hand second half of page back to the ring */
> ixgbe_reuse_rx_page(rx_ring, rx_buffer);
> } else {
> - if (!IS_ERR(skb) && IXGBE_CB(skb)->dma == rx_buffer->dma) {
> + if (skb && !xdp_res && IXGBE_CB(skb)->dma == rx_buffer->dma) {
xdp_res check is redundant here. skb ptr will be non-null only for xdp_res
== 0. so skb != NULL implies xdp_res == 0.
If I am not mistaken:D or ixgbe has some code path I missed.
Besides this, thanks for improving commit message!
> /* the page has been released from the ring */
> IXGBE_CB(skb)->page_released = true;
> } else {
> @@ -2415,7 +2415,8 @@ static int ixgbe_clean_rx_irq(struct ixgbe_q_vector *q_vector,
> break;
> }
>
> - ixgbe_put_rx_buffer(rx_ring, rx_buffer, skb, rx_buffer_pgcnt);
> + ixgbe_put_rx_buffer(rx_ring, rx_buffer, skb, rx_buffer_pgcnt,
> + xdp_res);
> cleaned_count++;
>
> /* place incomplete frames back on ring for completion */
> --
> v1 -> v2
> Provide extra details in commit message for motivation of this patch.
>
> 2.43.0
>
next prev parent reply other threads:[~2025-01-20 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 15:49 [PATCH iwl-next v2] ixgbe: Fix possible skb NULL pointer dereference Piotr Kwapulinski
2025-01-20 14:45 ` Maciej Fijalkowski [this message]
2025-01-23 8:19 ` Kwapulinski, Piotr
2025-01-23 12:27 ` Maciej Fijalkowski
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=Z45hfyEC6dE2Zkm3@boxer \
--to=maciej.fijalkowski@intel.com \
--cc=dan.carpenter@linaro.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.org \
--cc=piotr.kwapulinski@intel.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=yuehaibing@huawei.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;
as well as URLs for NNTP newsgroup(s).