linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Qian Cai <cai@lca.pw>
Cc: Dmitry Vyukov <dvyukov@google.com>,
	Amol Grover <frextrite@gmail.com>,
	Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com>,
	syzbot <syzbot+1519f497f2f9f08183c6@syzkaller.appspotmail.com>,
	David Miller <davem@davemloft.net>,
	kuba@kernel.org, Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
	LKML <linux-kernel@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
	Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	"paul E. McKenney" <paulmck@kernel.org>,
	"Joel Fernandes (Google)" <joel@joelfernandes.org>
Subject: Re: linux-next boot error: WARNING: suspicious RCU usage in ipmr_get_table
Date: Thu, 7 May 2020 06:26:01 +1000	[thread overview]
Message-ID: <20200507062601.7befefa6@canb.auug.org.au> (raw)
In-Reply-To: <20200507061635.449f9495@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 928 bytes --]

Hi all,

On Thu, 7 May 2020 06:16:35 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi Qian,
> 
> On Tue, 28 Apr 2020 09:56:59 -0400 Qian Cai <cai@lca.pw> wrote:
> >  
> > > On Apr 28, 2020, at 4:57 AM, Dmitry Vyukov <dvyukov@google.com> wrote:    
> > >> net/ipv4/ipmr.c:136 RCU-list traversed in non-reader section!!    
> > 
> > https://lore.kernel.org/netdev/20200222063835.14328-2-frextrite@gmail.com/
> > 
> > Never been picked up for a few months due to some reasons. You could probably
> > need to convince David, Paul, Steven or Linus to unblock the bot or carry patches
> > on your own?  
> 
> Did you resubmit the patch series as Dave Miller asked you to (now that
> net-next is based on v5.7-rc1+)?

In any case, I have added the 2 commits in this series to my fixes tree
from today - I will remove them when some other tree has a solution
applied.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2020-05-06 20:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000000000000df9a9805a455e07b@google.com>
2020-04-28  8:57 ` Dmitry Vyukov
2020-04-28 13:56   ` Qian Cai
2020-04-28 14:11     ` Madhuparna Bhowmik
2020-04-28 14:28       ` Qian Cai
2020-04-28 14:58         ` Madhuparna Bhowmik
2020-05-09  7:29         ` Amol Grover
2020-05-09  7:57           ` Madhuparna Bhowmik
2020-05-06 15:39     ` Amol Grover
2020-05-06 20:31       ` Stephen Rothwell
2020-05-06 20:16     ` Stephen Rothwell
2020-05-06 20:21       ` Qian Cai
2020-05-06 20:35         ` Stephen Rothwell
2020-05-06 20:26       ` Stephen Rothwell [this message]
2020-05-09  6:45         ` Amol Grover

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=20200507062601.7befefa6@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=cai@lca.pw \
    --cc=davem@davemloft.net \
    --cc=dvyukov@google.com \
    --cc=frextrite@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=kuba@kernel.org \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=madhuparnabhowmik10@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=syzbot+1519f497f2f9f08183c6@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=yoshfuji@linux-ipv6.org \
    --subject='Re: linux-next boot error: WARNING: suspicious RCU usage in ipmr_get_table' \
    /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

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).