Messages in this thread | | | Date | Wed, 20 Feb 2019 10:28:20 -0800 | From | "Paul E. McKenney" <> | Subject | Re: [RFC 0/5] RCU fixes for rcu_assign_pointer usage |
| |
On Wed, Feb 20, 2019 at 01:09:52PM -0500, Joel Fernandes wrote: > On Wed, Feb 20, 2019 at 08:42:43AM -0800, Paul E. McKenney wrote: > > 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@joelfernandes.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. > > Definitely will CC them next time, sorry about that. I'll stop being so shy > but I have some scars that are still healing ;-)
If you don't get at least a few scars, you aren't trying hard enough! ;-)
Thanx, Paul
| |