[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YzHlvsDcuji9CxpU@yury-laptop>
Date: Mon, 26 Sep 2022 10:47:42 -0700
From: Yury Norov <yury.norov@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>,
Rasmus Villemoes <linux@...musvillemoes.dk>
Subject: Re: [PATCH 2/7] net: fix cpu_max_bits_warn() usage in
netif_attrmask_next{,_and}
On Mon, Sep 26, 2022 at 10:34:37AM -0700, Jakub Kicinski wrote:
> On Mon, 19 Sep 2022 14:05:54 -0700 Yury Norov wrote:
> > The functions require to be passed with a cpu index prior to one that is
> > the first to start search, so the valid input range is [-1, nr_cpu_ids-1).
> > However, the code checks against [-1, nr_cpu_ids).
>
> Yup, the analysis looks correct:
>
> Acked-by: Jakub Kicinski <kuba@...nel.org>
Thanks. If no other comments from you and others, I'll take the series in
bitmap-for-next.
Powered by blists - more mailing lists