diff options
| author | Ingo Molnar <mingo@kernel.org> | 2020-10-09 09:21:56 +0300 |
|---|---|---|
| committer | Ingo Molnar <mingo@kernel.org> | 2020-10-09 09:21:56 +0300 |
| commit | b36c830f8c9b13bfe69b117e879153776c19ad82 (patch) | |
| tree | 151b7e91a49ff894e11e0b24c0e8cf9675dd5d91 /Documentation/RCU/Design/Data-Structures/Data-Structures.rst | |
| parent | 583090b1b8232e6eae243a9009699666153a13a9 (diff) | |
| parent | 6fe208f63a79f4f726f3be2b78ea3dd40487b657 (diff) | |
| download | linux-b36c830f8c9b13bfe69b117e879153776c19ad82.tar.xz | |
Merge branch 'for-mingo' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu into core/rcu
Pull v5.10 RCU changes from Paul E. McKenney:
- Debugging for smp_call_function().
- Strict grace periods for KASAN. The point of this series is to find
RCU-usage bugs, so the corresponding new RCU_STRICT_GRACE_PERIOD
Kconfig option depends on both DEBUG_KERNEL and RCU_EXPERT, and is
further disabled by dfefault. Finally, the help text includes
a goodly list of scary caveats.
- New smp_call_function() torture test.
- Torture-test updates.
- Documentation updates.
- Miscellaneous fixes.
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'Documentation/RCU/Design/Data-Structures/Data-Structures.rst')
| -rw-r--r-- | Documentation/RCU/Design/Data-Structures/Data-Structures.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/RCU/Design/Data-Structures/Data-Structures.rst b/Documentation/RCU/Design/Data-Structures/Data-Structures.rst index 4a48e20a46f2..f4efd6897b09 100644 --- a/Documentation/RCU/Design/Data-Structures/Data-Structures.rst +++ b/Documentation/RCU/Design/Data-Structures/Data-Structures.rst @@ -963,7 +963,7 @@ exit and perhaps also vice versa. Therefore, whenever the ``->dynticks_nesting`` field is incremented up from zero, the ``->dynticks_nmi_nesting`` field is set to a large positive number, and whenever the ``->dynticks_nesting`` field is decremented down to zero, -the the ``->dynticks_nmi_nesting`` field is set to zero. Assuming that +the ``->dynticks_nmi_nesting`` field is set to zero. Assuming that the number of misnested interrupts is not sufficient to overflow the counter, this approach corrects the ``->dynticks_nmi_nesting`` field every time the corresponding CPU enters the idle loop from process |