From: patchwork-bot+netdevbpf@kernel•org
To: Eric Dumazet <edumazet@google•com>
Cc: davem@davemloft•net, kuba@kernel•org, pabeni@redhat•com,
netdev@vger•kernel.org, eric.dumazet@gmail•com,
joshua.a.hay@intel•com, alan.brady@intel•com,
madhu.chittim@intel•com, phani.r.burra@intel•com,
sridhar.samudrala@intel•com, willemb@google•com,
pavan.kumar.linga@intel•com, anthony.l.nguyen@intel•com,
bcf@google•com
Subject: Re: [PATCH net] idpf: fix potential use-after-free in idpf_tso()
Date: Tue, 07 Nov 2023 01:30:25 +0000 [thread overview]
Message-ID: <169932062580.409.286762519826902863.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231103200451.514047-1-edumazet@google.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Fri, 3 Nov 2023 20:04:51 +0000 you wrote:
> skb_cow_head() can change skb->head (and thus skb_shinfo(skb))
>
> We must not cache skb_shinfo(skb) before skb_cow_head().
>
> Fixes: 6818c4d5b3c2 ("idpf: add splitq start_xmit")
> Signed-off-by: Eric Dumazet <edumazet@google•com>
> Cc: Joshua Hay <joshua.a.hay@intel•com>
> Cc: Alan Brady <alan.brady@intel•com>
> Cc: Madhu Chittim <madhu.chittim@intel•com>
> Cc: Phani Burra <phani.r.burra@intel•com>
> Cc: Sridhar Samudrala <sridhar.samudrala@intel•com>
> Cc: Willem de Bruijn <willemb@google•com>
> Cc: Pavan Kumar Linga <pavan.kumar.linga@intel•com>
> Cc: Tony Nguyen <anthony.l.nguyen@intel•com>
> Cc: Bailey Forrest <bcf@google•com>
>
> [...]
Here is the summary with links:
- [net] idpf: fix potential use-after-free in idpf_tso()
https://git.kernel.org/netdev/net/c/115c0f4d5857
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:[~2023-11-07 1:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 20:04 [PATCH net] idpf: fix potential use-after-free in idpf_tso() Eric Dumazet
2023-11-03 20:50 ` Jacob Keller
2023-11-07 1:30 ` 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=169932062580.409.286762519826902863.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=alan.brady@intel$(echo .)com \
--cc=anthony.l.nguyen@intel$(echo .)com \
--cc=bcf@google$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=joshua.a.hay@intel$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=madhu.chittim@intel$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=pavan.kumar.linga@intel$(echo .)com \
--cc=phani.r.burra@intel$(echo .)com \
--cc=sridhar.samudrala@intel$(echo .)com \
--cc=willemb@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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