linux-kernel - Re: Confused about hlist_unhashed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200131211950.GX2935@paulmck-ThinkPad-P72>
Date:   Fri, 31 Jan 2020 13:19:50 -0800
From:   "Paul E. McKenney" <paulmck@...nel.org>
To:     Eric Dumazet <edumazet@...gle.com>
Cc:     Peter Zijlstra <peterz@...radead.org>,
        Will Deacon <will@...nel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        the arch/x86 maintainers <x86@...nel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Marco Elver <elver@...gle.com>, mingo@...nel.org
Subject: Re: Confused about hlist_unhashed_lockless()

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@...nel.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@...gle.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