All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Haseeb Malik <haseebulhaq55@gmail.com>
Cc: sd@queasysnail.net, netdev@vger.kernel.org, davem@davemloft.net,
	linux-kernel@vger.kernel.org, edumazet@google.com,
	horms@kernel.org, kuba@kernel.org, andrew+netdev@lunn.ch,
	hangbin.liu@linux.dev, pabeni@redhat.com,
	syzkaller-bugs@googlegroups.com, felix.walter@cloudandheat.com,
	syzbot+f2f6312ad1b5a0bfe316@syzkaller.appspotmail.com
Subject: Re: [PATCH net v3] macsec: initialize SecY before registering the netdevice
Date: Thu, 24 Sep 2026 13:21:25 +0000	[thread overview]
Message-ID: <179025608572.1542893.3122720267052051951.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260921-fix-macsec-net-v3-1-accf94f93f5e@gmail.com>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Mon, 21 Sep 2026 16:40:30 -0400 you wrote:
> From: Haseeb Malik <haseebulhaq55@gmail.com>
> 
> Creating a MACsec device with MAC offload over an LRO-capable lower
> device triggers a warning in rtmsg_ifinfo_build_skb() when IPv4
> forwarding is enabled by default.
> 
> register_netdevice() invokes inetdev_init(), which disables LRO and emits
> a NETDEV_FEAT_CHANGE notification. This reaches macsec_fill_info() before
> macsec_add_dev() initializes the SecY. key_len is still zero, so
> macsec_fill_info() returns -EMSGSIZE and trips the WARN_ON in
> rtmsg_ifinfo_build_skb(), even though the skb has enough space.
> 
> [...]

Here is the summary with links:
  - [net,v3] macsec: initialize SecY before registering the netdevice
    https://git.kernel.org/netdev/net/c/c2de369c5c5b

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-09-24 13:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21 20:40 [PATCH net v3] macsec: initialize SecY before registering the netdevice Haseeb Malik
2026-09-21 20:40 ` Haseeb Malik via B4 Relay
2026-09-24 10:42 ` Sabrina Dubroca
2026-09-24 13:21 ` 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=179025608572.1542893.3122720267052051951.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=felix.walter@cloudandheat.com \
    --cc=hangbin.liu@linux.dev \
    --cc=haseebulhaq55@gmail.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sd@queasysnail.net \
    --cc=syzbot+f2f6312ad1b5a0bfe316@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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.