[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220928081509.2e169f4d@kernel.org>
Date: Wed, 28 Sep 2022 08:15:09 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Nikolay Aleksandrov <razor@...ckwall.org>
Cc: nicolas.dichtel@...nd.com,
Florent Fourcot <florent.fourcot@...irst.fr>,
netdev@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com,
pabeni@...hat.com, Johannes Berg <johannes@...solutions.net>,
Pablo Neira Ayuso <pablo@...filter.org>,
Florian Westphal <fw@...len.de>,
Jamal Hadi Salim <jhs@...atatu.com>,
Jacob Keller <jacob.e.keller@...el.com>,
Guillaume Nault <gnault@...hat.com>,
Hangbin Liu <liuhangbin@...il.com>
Subject: Re: [PATCH net-next] docs: netlink: clarify the historical baggage
of Netlink flags
On Wed, 28 Sep 2022 17:46:28 +0300 Nikolay Aleksandrov wrote:
> I like it, can't check right now if we can get into the same issue as with BULK where
> someone is passing unused/wrong flags with the command and we break him though.
So it'd only be effective for new commands, hopefully that's good
enough:
- if (hdr->cmd >= family->resv_start_op && hdr->reserved)
+ if (hdr->cmd >= family->resv_start_op && genl_header_check(nlh, hdr))
the resv_start_op thing I added in this cycle.
> But I'd bite the bullet and maybe issue an extack msg as well.
Fair point, more tests more magic. I'll add a msg.
Powered by blists - more mailing lists