All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ziwei Xiao <ziweixiao@google.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, jeroendb@google.com,
	pkaligineedi@google.com, shailend@google.com,
	hramamurthy@google.com, willemb@google.com, rushilg@google.com,
	bcf@google.com, csully@google.com, linux-kernel@vger.kernel.org,
	stable@kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net] gve: Clear napi->skb before dev_kfree_skb_any()
Date: Thu, 13 Jun 2024 14:40:31 +0000	[thread overview]
Message-ID: <171828963116.5991.16090491063036449379.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240612001654.923887-1-ziweixiao@google.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 12 Jun 2024 00:16:54 +0000 you wrote:
> gve_rx_free_skb incorrectly leaves napi->skb referencing an skb after it
> is freed with dev_kfree_skb_any(). This can result in a subsequent call
> to napi_get_frags returning a dangling pointer.
> 
> Fix this by clearing napi->skb before the skb is freed.
> 
> Fixes: 9b8dd5e5ea48 ("gve: DQO: Add RX path")
> Cc: stable@vger.kernel.org
> Reported-by: Shailend Chand <shailend@google.com>
> Signed-off-by: Ziwei Xiao <ziweixiao@google.com>
> Reviewed-by: Harshitha Ramamurthy <hramamurthy@google.com>
> Reviewed-by: Shailend Chand <shailend@google.com>
> Reviewed-by: Praveen Kaligineedi <pkaligineedi@google.com>
> 
> [...]

Here is the summary with links:
  - [net] gve: Clear napi->skb before dev_kfree_skb_any()
    https://git.kernel.org/netdev/net/c/6f4d93b78ade

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-06-13 14:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12  0:16 [PATCH net] gve: Clear napi->skb before dev_kfree_skb_any() Ziwei Xiao
2024-06-13 14:39 ` Jakub Kicinski
2024-06-13 14:40 ` 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=171828963116.5991.16090491063036449379.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bcf@google.com \
    --cc=csully@google.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hramamurthy@google.com \
    --cc=jeroendb@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pkaligineedi@google.com \
    --cc=rushilg@google.com \
    --cc=shailend@google.com \
    --cc=stable@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=willemb@google.com \
    --cc=ziweixiao@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.