linux-kernel - Re: [RFC 0/5] RCU fixes for rcu_assign

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: <20190220164242.GN11787@linux.ibm.com>
Date:   Wed, 20 Feb 2019 08:42:43 -0800
From:   "Paul E. McKenney" <paulmck@...ux.ibm.com>
To:     Joel Fernandes <joel@...lfernandes.org>
Cc:     LKML <linux-kernel@...r.kernel.org>, rcu@...r.kernel.org
Subject: Re: [RFC 0/5] RCU fixes for rcu_assign_pointer usage

On Tue, Feb 19, 2019 at 08:11:36PM -0800, Joel Fernandes wrote:
> On Tue, Feb 19, 2019 at 8:08 PM Joel Fernandes (Google)
> <joel@...lfernandes.org> wrote:
> >
> > These patches fix various RCU API usage issues found due to sparse errors as a
> > result of the recent check to add rcu_check_sparse() to rcu_assign_pointer().
> >
> > This is very early RFC stage, and is only build tested. I am also only sending
> > to the RCU group for initial review before sending to LKML. Thanks for any feedback!
> >
> > There are still more usages that cause errors such as rbtree which I am
> > looking into.
> 
> Looks like it got sent to LKML anyway, ;-) That's Ok since it is
> prefixed as RFC.

As is only right and proper.  ;-)

I don't see an immediate problem with them, but it would be good to get
the relevant developers and maintainers on CC for the next version.  I
cannot claim to know that code very well.

							Thanx, Paul