[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221019153452.2679589-1-alexandr.lobakin@intel.com>
Date: Wed, 19 Oct 2022 17:34:52 +0200
From: Alexander Lobakin <alexandr.lobakin@...el.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Alexander Lobakin <alexandr.lobakin@...el.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>,
Yury Norov <yury.norov@...il.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Rasmus Villemoes <linux@...musvillemoes.dk>,
Michal Swiatkowski <michal.swiatkowski@...ux.intel.com>,
Maciej Fijalkowski <maciej.fijalkowski@...el.com>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 net-next 6/6] netlink: add universal 'bigint' attribute type
From: Jakub Kicinski <kuba@...nel.org>
Date: Tue, 18 Oct 2022 12:53:58 -0700
> On Tue, 18 Oct 2022 16:00:27 +0200 Alexander Lobakin wrote:
> > @@ -235,12 +236,15 @@ enum nla_policy_validation {
> > * given type fits, using it verifies minimum length
> > * just like "All other"
> > * NLA_BITFIELD32 Unused
> > + * NLA_BIGINT Number of bits in the big integer
[...]
> > + break;
> > +
>
> Very good stuff, the validation vs type separation is the big question.
Another round of great comments, copied to the TODO. Will dig out
everything and return with v3, for now at least most of those sound
possible and reasonable.
Thanks,
Olek
Powered by blists - more mailing lists