From: Alasdair McWilliam <alasdair@mcwilliam.dev>
To: Daniel Borkmann <daniel@iogearbox.net>, netdev@vger.kernel.org
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH] rtnetlink: add needed_{head,tail}room attributes
Date: Tue, 16 Sep 2025 11:56:30 +0100 [thread overview]
Message-ID: <79587f3e-8f23-4a6b-af25-901364d8530d@mcwilliam.dev> (raw)
In-Reply-To: <e742f9e0-671d-4058-99af-c3e38b73ec0d@iogearbox.net>
Hi Daniel,
On 15/09/2025 17:49, Daniel Borkmann wrote:
> Hi Alasdair,
>
>> @@ -2243,6 +2249,8 @@ static const struct nla_policy
>> ifla_policy[IFLA_MAX+1] = {
>> [IFLA_GSO_IPV4_MAX_SIZE] = NLA_POLICY_MIN(NLA_U32,
>> MAX_TCP_HEADER + 1),
>> [IFLA_GRO_IPV4_MAX_SIZE] = { .type = NLA_U32 },
>> [IFLA_NETNS_IMMUTABLE] = { .type = NLA_REJECT },
>> + [IFLA_HEADROOM] = { .type = NLA_U16 },
>> + [IFLA_TAILROOM] = { .type = NLA_U16 },
>
> Given this is for dumping only, we'd need to replace NLA_U16 above with
> NLA_REJECT
> like in case of IFLA_NETNS_IMMUTABLE.
>
> Also the Documentation/netlink/specs/rt_link.yaml needs an extension,
> otherwise lgtm.
> $subj should have [PATCH net-next] to indicate the target tree.
>
Acknowledged. I will revise and re-submit. I will also include
additional context in the commit log as per your later email in this thread.
> Thanks,
> Daniel
Thanks!
Alasdair
prev parent reply other threads:[~2025-09-16 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 16:32 [PATCH] rtnetlink: add needed_{head,tail}room attributes Alasdair McWilliam
2025-09-15 16:49 ` Daniel Borkmann
2025-09-15 17:20 ` Stephen Hemminger
2025-09-15 18:30 ` Daniel Borkmann
2025-09-16 10:56 ` Alasdair McWilliam [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=79587f3e-8f23-4a6b-af25-901364d8530d@mcwilliam.dev \
--to=alasdair@mcwilliam.dev \
--cc=andrew+netdev@lunn.ch \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.