All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Yury Norov <yury.norov@gmail.com>, Borislav Petkov <bp@alien8.de>,
	syzbot <syzbot+d0fd2bf0dd6da72496dd@syzkaller.appspotmail.com>,
	syzkaller-bugs@googlegroups.com,
	Andrew Jones <ajones@ventanamicro.com>,
	netdev@vger.kernel.org, "David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Menglong Dong <imagedong@tencent.com>,
	Kuniyuki Iwashima <kuniyu@amazon.com>,
	Petr Machata <petrm@nvidia.com>,
	Guo Ren <guoren@linux.alibaba.com>,
	"Michael S . Tsirkin" <mst@redhat.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	andriy.shevchenko@linux.intel.com, linux@rasmusvillemoes.dk,
	caraitto@google.com, willemb@google.com, jonolson@google.com,
	amritha.nambiar@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [syzbot] WARNING in c_start
Date: Mon, 17 Oct 2022 14:26:41 -0700	[thread overview]
Message-ID: <20221017142641.26fc370c@kernel.org> (raw)
In-Reply-To: <50e2ecf5-4b83-3ba1-70a2-796d988d4c0b@I-love.SAKURA.ne.jp>

On Mon, 17 Oct 2022 11:54:01 +0900 Tetsuo Handa wrote:
> On 2022/10/17 2:52, Linus Torvalds wrote:
> > Anyway, since rc1 is fairly imminent, I will just revert it for now -
> > I don't want to have a pending revert wait until -rc2.  
> 
> Thank you, Linus.
> 
> Yury or Jakub, please send a revert request on commit 854701ba4c39 ("net: fix cpu_max_bits_warn()
> usage in netif_attrmask_next{,_and}"), for https://syzkaller.appspot.com/bug?extid=9abe5ecc348676215427
> says that boot is still failing.

Yup, we got that revert queued up. LMK if it's a show stopper 
otherwise it'll get to Linus on Thu.

      reply	other threads:[~2022-10-17 21:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14 21:16 [syzbot] WARNING in c_start syzbot
2022-10-14 21:24 ` Borislav Petkov
     [not found]   ` <2eaf1386-8ab0-bd65-acee-e29f1c5a6623@I-love.SAKURA.ne.jp>
     [not found]     ` <Y0qfLyhSoTodAdxu@zn.tnic>
2022-10-15 20:44       ` Yury Norov
2022-10-16  0:24         ` Tetsuo Handa
2022-10-16  0:28           ` Randy Dunlap
2022-10-16  0:34             ` Tetsuo Handa
2022-10-16  1:12           ` Yury Norov
2022-10-16  4:10             ` Tetsuo Handa
2022-10-16 17:52             ` Linus Torvalds
2022-10-17  2:54               ` Tetsuo Handa
2022-10-17 21:26                 ` Jakub Kicinski [this message]

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=20221017142641.26fc370c@kernel.org \
    --to=kuba@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=ajones@ventanamicro.com \
    --cc=amritha.nambiar@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bigeasy@linutronix.de \
    --cc=bp@alien8.de \
    --cc=caraitto@google.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=guoren@linux.alibaba.com \
    --cc=imagedong@tencent.com \
    --cc=jonolson@google.com \
    --cc=kuniyu@amazon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=petrm@nvidia.com \
    --cc=syzbot+d0fd2bf0dd6da72496dd@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=torvalds@linux-foundation.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.