From: Joel Fernandes <joel@joelfernandes•org>
To: linux-kernel@vger•kernel.org
Cc: Alexey Kuznetsov <kuznet@ms2•inr.ac.ru>,
Bjorn Helgaas <bhelgaas@google•com>,
Borislav Petkov <bp@alien8•de>,
c0d1n61at3@gmail•com, "David S. Miller" <davem@davemloft•net>,
edumazet@google•com,
Greg Kroah-Hartman <gregkh@linuxfoundation•org>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6•org>,
"H. Peter Anvin" <hpa@zytor•com>, Ingo Molnar <mingo@redhat•com>,
Josh Triplett <josh@joshtriplett•org>,
keescook@chromium•org, kernel-hardening@lists•openwall.com,
Lai Jiangshan <jiangshanlai@gmail•com>,
Len Brown <lenb@kernel•org>,
linux-acpi@vger•kernel.org, linux-pci@vger•kernel.org,
linux-pm@vger•kernel.org,
Mathieu Desnoyers <mathieu.desnoyers@efficios•com>,
neilb@suse•com, netdev@vger•kernel.org, oleg@redhat•com,
"Paul E. McKenney" <paulmck@linux•ibm.com>,
Pavel Machek <pavel@ucw•cz>,
peterz@infradead•org, "Rafael J. Wysocki" <rjw@rjwysocki•net>,
Rasmus Villemoes <rasmus.villemoes@prevas•dk>,
rcu@vger•kernel.org, Steven Rostedt <rostedt@goodmis•org>,
Tejun Heo <tj@kernel•org>, Thomas Gleixner <tglx@linutronix•de>,
will@kernel•org,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel•org>
Subject: Re: [PATCH v1 0/6] Harden list_for_each_entry_rcu() and family
Date: Thu, 11 Jul 2019 19:52:39 -0400 [thread overview]
Message-ID: <20190711235239.GA221389@google.com> (raw)
In-Reply-To: <20190711234401.220336-1-joel@joelfernandes.org>
On Thu, Jul 11, 2019 at 07:43:55PM -0400, Joel Fernandes (Google) wrote:
> Hi,
> This series aims to provide lockdep checking to RCU list macros.
>
> RCU has a number of primitives for "consumption" of an RCU protected pointer.
> Most of the time, these consumers make sure that such accesses are under a RCU
> reader-section (such as rcu_dereference{,sched,bh} or under a lock, such as
> with rcu_dereference_protected()).
>
> However, there are other ways to consume RCU pointers, such as by
> list_for_each_entry_rcu or hlist_for_each_enry_rcu. Unlike the rcu_dereference
> family, these consumers do no lockdep checking at all. And with the growing
> number of RCU list uses (1000+), it is possible for bugs to creep in and go
> unnoticed which lockdep checks can catch.
I forgot to add in my cover letter, I have kept this option default-disabled
under a new config: CONFIG_PROVE_RCU_LIST. This is so that until all users
are converted to pass the optional argument, we should keep the check
disabled. There are about a 1000 or so users and it is not possible to pass
in the optional lockdep expression in a single series since it is done on a
case-by-case basis. I did convert a few users in this series itself.
Also, I plans to update the RCU documentation as well which I will do, but do
review this series and thank you!
prev parent reply other threads:[~2019-07-11 23:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 23:43 [PATCH v1 0/6] Harden list_for_each_entry_rcu() and family Joel Fernandes (Google)
2019-07-11 23:43 ` [PATCH v1 1/6] rcu: Add support for consolidated-RCU reader checking Joel Fernandes (Google)
2019-07-12 4:49 ` Joel Fernandes
2019-07-12 11:01 ` Peter Zijlstra
2019-07-12 14:49 ` Joel Fernandes
2019-07-12 11:11 ` Peter Zijlstra
2019-07-12 15:10 ` Joel Fernandes
2019-07-12 15:58 ` Peter Zijlstra
2019-07-12 16:45 ` Paul E. McKenney
2019-07-12 17:06 ` Joel Fernandes
2019-07-12 17:46 ` Paul E. McKenney
2019-07-12 19:40 ` Joel Fernandes
2019-07-12 23:27 ` Paul E. McKenney
2019-07-12 12:12 ` Oleg Nesterov
2019-07-12 13:56 ` Joel Fernandes
2019-07-11 23:43 ` [PATCH v1 2/6] ipv4: add lockdep condition to fix for_each_entry Joel Fernandes (Google)
2019-07-11 23:43 ` [PATCH v1 3/6] driver/core: Convert to use built-in RCU list checking Joel Fernandes (Google)
2019-07-12 5:19 ` Greg Kroah-Hartman
2019-07-11 23:43 ` [PATCH v1 4/6] workqueue: Convert for_each_wq to use built-in list check Joel Fernandes (Google)
2019-07-11 23:44 ` [PATCH v1 5/6] x86/pci: Pass lockdep condition to pcm_mmcfg_list iterator Joel Fernandes (Google)
2019-07-11 23:44 ` [PATCH v1 6/6] acpi: Use built-in RCU list checking for acpi_ioremaps list Joel Fernandes (Google)
2019-07-11 23:52 ` Joel Fernandes [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=20190711235239.GA221389@google.com \
--to=joel@joelfernandes$(echo .)org \
--cc=bhelgaas@google$(echo .)com \
--cc=bp@alien8$(echo .)de \
--cc=c0d1n61at3@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=hpa@zytor$(echo .)com \
--cc=jiangshanlai@gmail$(echo .)com \
--cc=josh@joshtriplett$(echo .)org \
--cc=keescook@chromium$(echo .)org \
--cc=kernel-hardening@lists$(echo .)openwall.com \
--cc=kuznet@ms2$(echo .)inr.ac.ru \
--cc=lenb@kernel$(echo .)org \
--cc=linux-acpi@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-pci@vger$(echo .)kernel.org \
--cc=linux-pm@vger$(echo .)kernel.org \
--cc=mathieu.desnoyers@efficios$(echo .)com \
--cc=mingo@redhat$(echo .)com \
--cc=neilb@suse$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=oleg@redhat$(echo .)com \
--cc=paulmck@linux$(echo .)ibm.com \
--cc=pavel@ucw$(echo .)cz \
--cc=peterz@infradead$(echo .)org \
--cc=rasmus.villemoes@prevas$(echo .)dk \
--cc=rcu@vger$(echo .)kernel.org \
--cc=rjw@rjwysocki$(echo .)net \
--cc=rostedt@goodmis$(echo .)org \
--cc=tglx@linutronix$(echo .)de \
--cc=tj@kernel$(echo .)org \
--cc=will@kernel$(echo .)org \
--cc=x86@kernel$(echo .)org \
--cc=yoshfuji@linux-ipv6$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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