From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
willemb@google.com, horms@kernel.org, netdev@vger.kernel.org,
stable@vger.kernel.org, anthony.l.nguyen@intel.com,
przemyslaw.kitszel@intel.com, andrew+netdev@lunn.ch
Subject: Re: [PATCH net] ixgbe: reserve TX timestamp after skb preparation
Date: Tue, 27 Oct 2026 11:40:04 +0000 [thread overview]
Message-ID: <179310120441.3755414.16229460906940090919.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261026082035.335770-1-edumazet@kernel.org>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 26 Oct 2026 09:20:35 +0100 you wrote:
> ixgbe_xmit_frame_ring() takes an extra skb reference with skb_get()
> for the pending TX timestamp before preparing the skb for transmit.
> Several of the following steps may need to reallocate the skb head:
>
> - ixgbe_tso() calls skb_cow_head(), which reaches pskb_expand_head()
> when the header is cloned (e.g. a packet tap holds a clone).
> - ixgbe_tx_csum() falls back to skb_checksum_help() for unsupported
> checksum offsets, which can call pskb_expand_head() through
> skb_ensure_writable().
> - With DCB and a software VLAN tag, skb_cow_head() is called to
> rewrite the VLAN priority.
>
> [...]
Here is the summary with links:
- [net] ixgbe: reserve TX timestamp after skb preparation
https://git.kernel.org/netdev/net/c/f75062536e2d
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:[~2026-10-27 11:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 8:20 [PATCH net] ixgbe: reserve TX timestamp after skb preparation Eric Dumazet
2026-10-26 8:26 ` netdev-bot+sinfo
2026-10-26 8:49 ` Eric Dumazet
2026-10-26 13:42 ` Maciej Fijalkowski
2026-10-27 11: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=179310120441.3755414.16229460906940090919.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=stable@vger.kernel.org \
--cc=willemb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox