netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Yury Norov <yury.norov@gmail.com>
Cc: guoren@kernel.org, andriy.shevchenko@linux.intel.com,
	davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
	linux@rasmusvillemoes.dk, caraitto@google.com,
	willemb@google.com, jonolson@google.com,
	amritha.nambiar@intel.com, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, Guo Ren <guoren@linux.alibaba.com>
Subject: Re: [PATCH V2 1/2] net: Fixup netif_attrmask_next_and warning
Date: Fri, 14 Oct 2022 09:03:11 -0700	[thread overview]
Message-ID: <20221014090311.392e0546@kernel.org> (raw)
In-Reply-To: <Y0jowX4zIZMMVc0H@yury-laptop>

On Thu, 13 Oct 2022 21:42:41 -0700 Yury Norov wrote:
> > Oh, it was reposted today:
> > 
> > https://lore.kernel.org/all/20221013234349.1165689-2-yury.norov@gmail.com/
> > 
> > But we need a revert of 854701ba4c as well to cover the issue back up
> > for 6.1, AFAIU.  
> 
> The patch 854701ba4c is technically correct. I fixed most of warnings in
> advance, but nobody can foresee everything, right? I expected some noise,
> and now we have just a few things to fix.

I got 6 warnings booting my machine after pulling back from Linus
(which included your patches in net for the first time).
And that's not including the XPS and the virtio warning.

> This is what for -rc releases exist, didn't they?
> 
> I suggest to keep the patch, because this is the only way to make
> cpumask_check()-related issues visible to people. If things will go as
> they go now, I expect that -rc3 will be clean from cpumask_check()
> warnings.

This sounds too close to saying that "it's okay for -rc1 to be broken".
Why were your changes not in linux-next for a month before the merge
window? :(

We will not be merging a refactoring series into net to silence an
arguably over-eager warning. We need a minimal fix, Guo Ren's patches
seem to miss the mark so I reckon the best use of everyone's time is 
to just drop the exposing patch and retry in -next 🤷

  parent reply	other threads:[~2022-10-14 16:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14  3:04 [PATCH V2 0/2] net: Fixup cpu_mask usage guoren
2022-10-14  3:04 ` [PATCH V2 1/2] net: Fixup netif_attrmask_next_and warning guoren
2022-10-14  3:35   ` Jakub Kicinski
2022-10-14  3:39     ` Jakub Kicinski
2022-10-14  4:42       ` Yury Norov
2022-10-14  6:42         ` Guo Ren
2022-10-14 16:03         ` Jakub Kicinski [this message]
2022-10-14 16:16           ` Yury Norov
2022-10-14 18:03             ` Jakub Kicinski
2022-10-15  1:41           ` Guo Ren
2022-10-14  6:38     ` Guo Ren
2022-10-14 15:52       ` Jakub Kicinski
2022-10-15  1:38         ` Guo Ren
2022-10-14 10:00   ` Andy Shevchenko
2022-10-14 10:04     ` Guo Ren
2022-10-14  3:04 ` [PATCH V2 2/2] net: Fixup virtnet_set_affinity() cause cpumask warning guoren
2022-10-14 10:00   ` Andy Shevchenko
2022-10-14 10:04     ` Guo Ren
2022-10-17  1:58   ` Xuan Zhuo
2022-10-17  2:46     ` Guo Ren
2022-10-17  2:58       ` Xuan Zhuo

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=20221014090311.392e0546@kernel.org \
    --to=kuba@kernel.org \
    --cc=amritha.nambiar@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=caraitto@google.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=guoren@kernel.org \
    --cc=guoren@linux.alibaba.com \
    --cc=jonolson@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=willemb@google.com \
    --cc=yury.norov@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).