[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y0kzKgHO51LlqGkY@smile.fi.intel.com>
Date: Fri, 14 Oct 2022 13:00:10 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: guoren@...nel.org
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, linux@...musvillemoes.dk, yury.norov@...il.com,
caraitto@...gle.com, willemb@...gle.com, jonolson@...gle.com,
amritha.nambiar@...el.com, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, Guo Ren <guoren@...ux.alibaba.com>
Subject: Re: [PATCH V2 2/2] net: Fixup virtnet_set_affinity() cause cpumask
warning
On Thu, Oct 13, 2022 at 11:04:59PM -0400, guoren@...nel.org wrote:
> From: Guo Ren <guoren@...ux.alibaba.com>
>
> Don't pass nr_bits-1 as arg1 for cpumask_next_wrap, which would
> cause warning now 78e5a3399421 ("cpumask: fix checking valid
> cpu range").
> ------------[ cut here ]------------
> WARNING: CPU: 0 PID: 1 at include/linux/cpumask.h:110 cpumask_next_wrap+0x5c/0x80
> Modules linked in:
Submitting Patches document suggests to cut this huge warning to only what
makes sense to see in the report.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists