All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Elver <elver@google.com>
To: paulmck@kernel.org
Cc: syzbot <syzbot+4dfb96a94317a78f44d9@syzkaller.appspotmail.com>,
	rcu@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	viro@zeniv.linux.org.uk
Subject: Re: [syzbot] KCSAN: data-race in call_rcu / rcu_gp_fqs_loop
Date: Tue, 26 Oct 2021 16:39:44 +0200	[thread overview]
Message-ID: <CANpmjNPu876ApAQzODM3OCY0uitkw9SuucNcpW9gRq19rrjuGQ@mail.gmail.com> (raw)
In-Reply-To: <20211026143337.GA1861432@paulmck-ThinkPad-P17-Gen-1>

On Tue, 26 Oct 2021 at 16:33, Paul E. McKenney <paulmck@kernel.org> wrote:
> On Tue, Oct 26, 2021 at 07:07:30AM -0700, Paul E. McKenney wrote:
> > On Mon, Oct 25, 2021 at 12:31:53PM +0200, Marco Elver wrote:
> > > +Cc Paul
> > >
> > > data race is in rcu code, presumably not yet discovered by rcutorture?
> >
> > Quite possibly, and I will take a look.  Thank you for sending this
> > along.
>
> And this is (allegedly) fixed by commit 2431774f04d10 ("rcu: Mark accesses
> to rcu_state.n_force_qs"), which is in -rcu and slated for the upcoming
> merge window.  But yes, still a bug in mainline.

Thanks for confirming, then the latest incarnation of it must then be
a dup, and I'll mark it fixed:

#syz fix: rcu: Mark accesses to rcu_state.n_force_qs

Apologies I missed there was a previous report and your fix.

Thanks,
-- Marco

      reply	other threads:[~2021-10-26 14:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25 10:29 [syzbot] KCSAN: data-race in call_rcu / rcu_gp_fqs_loop syzbot
2021-10-25 10:31 ` Marco Elver
2021-10-26 14:07   ` Paul E. McKenney
2021-10-26 14:33     ` Paul E. McKenney
2021-10-26 14:39       ` Marco Elver [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=CANpmjNPu876ApAQzODM3OCY0uitkw9SuucNcpW9gRq19rrjuGQ@mail.gmail.com \
    --to=elver@google.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=rcu@vger.kernel.org \
    --cc=syzbot+4dfb96a94317a78f44d9@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=viro@zeniv.linux.org.uk \
    /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.