All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, netdev@vger.kernel.org, eric.dumazet@gmail.com,
	syzbot+1f9fd0f4b601cf88d6e6@syzkaller.appspotmail.com,
	xietangxin@h-partners.com
Subject: Re: [PATCH v2 net] ipvlan: inherit needed_headroom and needed_tailroom from phy_dev
Date: Mon, 10 Aug 2026 22:40:17 +0000	[thread overview]
Message-ID: <178640161764.238814.13057537742776520230.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260806103857.115541-1-edumazet@google.com>

Hello:

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

On Thu,  6 Aug 2026 10:38:57 +0000 you wrote:
> ipvlan devices inherit hard_header_len from phy_dev during ipvlan_init(),
> but leave needed_headroom and needed_tailroom set to 0.
> 
> When the underlying phy_dev (or stacked lower device) requires extra headroom
> or tailroom for headers/trailers (e.g. macsec, ipsec, wireguard, tunnels, or
> veth with rx headroom), upper layers calculating packet headroom and tailroom
> fail to reserve sufficient space.
> 
> [...]

Here is the summary with links:
  - [v2,net] ipvlan: inherit needed_headroom and needed_tailroom from phy_dev
    https://git.kernel.org/netdev/net/c/e16e960d55a4

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



      parent reply	other threads:[~2026-08-10 22:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06 10:38 [PATCH v2 net] ipvlan: inherit needed_headroom and needed_tailroom from phy_dev Eric Dumazet
2026-08-07  6:23 ` Hangbin Liu
2026-08-10 22: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=178640161764.238814.13057537742776520230.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzbot+1f9fd0f4b601cf88d6e6@syzkaller.appspotmail.com \
    --cc=xietangxin@h-partners.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.