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
| ||
|
Date: Fri, 09 Oct 2020 06:35:45 -0000 From: "tip-bot2 for Randy Dunlap" <tip-bot2@...utronix.de> To: linux-tip-commits@...r.kernel.org Cc: Randy Dunlap <rdunlap@...radead.org>, Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org, "Paul E. McKenney" <paulmck@...nel.org>, Josh Triplett <josh@...htriplett.org>, Steven Rostedt <rostedt@...dmis.org>, Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, Lai Jiangshan <jiangshanlai@...il.com>, Joel Fernandes <joel@...lfernandes.org>, rcu@...r.kernel.org, x86 <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org> Subject: [tip: core/rcu] doc: Drop doubled words from RCU requirements documentation The following commit has been merged into the core/rcu branch of tip: Commit-ID: 7f45d6f8ae383ed01070883b3c74ee51c9740065 Gitweb: https://git.kernel.org/tip/7f45d6f8ae383ed01070883b3c74ee51c9740065 Author: Randy Dunlap <rdunlap@...radead.org> AuthorDate: Fri, 03 Jul 2020 14:33:42 -07:00 Committer: Paul E. McKenney <paulmck@...nel.org> CommitterDate: Mon, 24 Aug 2020 14:29:17 -07:00 doc: Drop doubled words from RCU requirements documentation Drop the doubled words "to" and "for". Signed-off-by: Randy Dunlap <rdunlap@...radead.org> Cc: Jonathan Corbet <corbet@....net> Cc: linux-doc@...r.kernel.org Cc: "Paul E. McKenney" <paulmck@...nel.org> Cc: Josh Triplett <josh@...htriplett.org> Cc: Steven Rostedt <rostedt@...dmis.org> Cc: Mathieu Desnoyers <mathieu.desnoyers@...icios.com> Cc: Lai Jiangshan <jiangshanlai@...il.com> Cc: Joel Fernandes <joel@...lfernandes.org> Cc: rcu@...r.kernel.org Signed-off-by: Paul E. McKenney <paulmck@...nel.org> --- Documentation/RCU/Design/Requirements/Requirements.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/RCU/Design/Requirements/Requirements.rst b/Documentation/RCU/Design/Requirements/Requirements.rst index 8f41ad0..1ae79a1 100644 --- a/Documentation/RCU/Design/Requirements/Requirements.rst +++ b/Documentation/RCU/Design/Requirements/Requirements.rst @@ -2162,7 +2162,7 @@ scheduling-clock interrupt be enabled when RCU needs it to be: this sort of thing. #. If a CPU is in a portion of the kernel that is absolutely positively no-joking guaranteed to never execute any RCU read-side critical - sections, and RCU believes this CPU to to be idle, no problem. This + sections, and RCU believes this CPU to be idle, no problem. This sort of thing is used by some architectures for light-weight exception handlers, which can then avoid the overhead of ``rcu_irq_enter()`` and ``rcu_irq_exit()`` at exception entry and @@ -2431,7 +2431,7 @@ However, there are legitimate preemptible-RCU implementations that do not have this property, given that any point in the code outside of an RCU read-side critical section can be a quiescent state. Therefore, *RCU-sched* was created, which follows “classic” RCU in that an -RCU-sched grace period waits for for pre-existing interrupt and NMI +RCU-sched grace period waits for pre-existing interrupt and NMI handlers. In kernels built with ``CONFIG_PREEMPT=n``, the RCU and RCU-sched APIs have identical implementations, while kernels built with ``CONFIG_PREEMPT=y`` provide a separate implementation for each.
Powered by blists - more mailing lists