From: "Paul E. McKenney" <paulmck@kernel.org>
To: Eric Dumazet <edumazet@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Will Deacon <will@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
the arch/x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Marco Elver <elver@google.com>,
mingo@kernel.org
Subject: Re: Confused about hlist_unhashed_lockless()
Date: Fri, 31 Jan 2020 13:19:50 -0800 [thread overview]
Message-ID: <20200131211950.GX2935@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <CANn89iJzzws6MbbwuwXs+GPHAe3X-jB=JnKLh_6bX76keoKLwA@mail.gmail.com>
On Fri, Jan 31, 2020 at 01:04:37PM -0800, Eric Dumazet wrote:
> On Fri, Jan 31, 2020 at 12:53 PM Paul E. McKenney <paulmck@kernel.org> wrote:
> >
> > On Fri, Jan 31, 2020 at 10:52:46AM -0800, Eric Dumazet wrote:
> > > On Fri, Jan 31, 2020 at 10:48 AM Eric Dumazet <edumazet@google.com> wrote:
> > > >
> > >
> > > > This is nice, now with have data_race()
> > > >
> > > > Remember these patches were sent 2 months ago, at a time we were
> > > > trying to sort out things.
> > > >
> > > > data_race() was merged a few days ago.
> > >
> > > Well, actually data_race() is not there yet anyway.
> > >
> > > Is it really scheduled for 5.7 kernel ?
> >
> > Right now, yes. Would it make sense to separate it out and push it
> > into the current merge window?
>
> That would be very nice, because we could start using it before KCSAN is merged.
Seems reasonable to me. This one is already inn -tip:
c48981eeb0d5 ("include/linux/compiler.h: Introduce data_race(expr) macro")
This is in tip/WIP.locking/kcsan, so I am adding Ingo on CC.
Ingo, how would you like to proceed? For example, if it would be
helpful, I could rebase that commit on top of rcu/for-mingo and send a
pull request.
Thanx, Paul
next prev parent reply other threads:[~2020-01-31 21:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 16:43 Will Deacon
2020-01-31 16:48 ` Eric Dumazet
2020-01-31 16:57 ` Will Deacon
2020-01-31 17:06 ` Eric Dumazet
2020-01-31 17:20 ` Will Deacon
2020-01-31 17:33 ` Eric Dumazet
2020-01-31 18:32 ` Will Deacon
2020-01-31 19:47 ` Thomas Gleixner
2020-01-31 20:52 ` Paul E. McKenney
2020-01-31 18:43 ` Peter Zijlstra
2020-01-31 18:48 ` Eric Dumazet
2020-01-31 18:52 ` Eric Dumazet
2020-01-31 20:53 ` Paul E. McKenney
2020-01-31 21:04 ` Eric Dumazet
2020-01-31 21:19 ` Paul E. McKenney [this message]
2020-02-03 15:45 ` David Laight
2020-02-03 15:54 ` Marco Elver
2020-02-03 16:05 ` David Laight
2020-02-03 17:25 ` Paul E. McKenney
2020-02-03 15:58 ` Paul E. McKenney
2020-02-03 16:02 ` Will Deacon
2020-02-03 17:29 ` Paul E. McKenney
2020-02-03 18:27 ` Will Deacon
2020-02-03 21:16 ` Paul E. McKenney
2020-01-31 19:20 ` Marco Elver
2020-01-31 18:52 ` Paul E. McKenney
2020-01-31 18:55 ` Eric Dumazet
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=20200131211950.GX2935@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=edumazet@google.com \
--cc=elver@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®