public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Benjamin Poirier <bpoirier@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, idosch@nvidia.com,
	razor@blackwall.org, horms@kernel.org, jbenc@redhat.com,
	gavinl@nvidia.com, liuhangbin@gmail.com, vladimir@nikishkin.pw,
	lizetao1@huawei.com, tgraf@suug.ch, therbert@google.com,
	roopa@nvidia.com
Subject: Re: [PATCH net] vxlan: Add missing entries to vxlan_get_size()
Date: Wed, 20 Sep 2023 08:10:22 +0000	[thread overview]
Message-ID: <169519742236.8735.10821506861511564714.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230918154015.80722-1-bpoirier@nvidia.com>

Hello:

This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:

On Mon, 18 Sep 2023 11:40:15 -0400 you wrote:
> There are some attributes added by vxlan_fill_info() which are not
> accounted for in vxlan_get_size(). Add them.
> 
> I didn't find a way to trigger an actual problem from this miscalculation
> since there is usually extra space in netlink size calculations like
> if_nlmsg_size(); but maybe I just didn't search long enough.
> 
> [...]

Here is the summary with links:
  - [net] vxlan: Add missing entries to vxlan_get_size()
    https://git.kernel.org/netdev/net/c/4e4b1798cc90

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



      parent reply	other threads:[~2023-09-20  8:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 15:40 [PATCH net] vxlan: Add missing entries to vxlan_get_size() Benjamin Poirier
2023-09-18 18:40 ` Nikolay Aleksandrov
2023-09-19 15:20 ` Ido Schimmel
2023-09-20  8:10 ` 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=169519742236.8735.10821506861511564714.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bpoirier@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gavinl@nvidia.com \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=jbenc@redhat.com \
    --cc=kuba@kernel.org \
    --cc=liuhangbin@gmail.com \
    --cc=lizetao1@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=razor@blackwall.org \
    --cc=roopa@nvidia.com \
    --cc=tgraf@suug.ch \
    --cc=therbert@google.com \
    --cc=vladimir@nikishkin.pw \
    /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