doc: RCU: Adopt new coding style of type-aware kmalloc-family - part 2/2

Update Documentation/RCU/* to suggest using the new type-aware
kmalloc_obj() per commit 2932ba8d9c ("slab: Introduce kmalloc_obj()
and family")

p = kmalloc(...);
 -> p = kmalloc_obj(...);

Signed-off-by: Manuel Ebner <manuelebner@mailbox.org>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
This commit is contained in:
Manuel Ebner
2026-06-27 11:06:06 +02:00
committed by Paul E. McKenney
parent 573d76f7db
commit dc7e119abd

View File

@@ -236,7 +236,7 @@ precautions. To see this, consider the following code fragment::
{
struct foo *p;
p = kmalloc(...);
p = kmalloc_obj(*p);
if (p == NULL)
deal_with_it();
p->a = 42; /* Each field in its own cache line. */
@@ -293,7 +293,7 @@ Then one approach is to use locking, for example, as follows::
{
struct foo *p;
p = kmalloc(...);
p = kmalloc_obj(*p);
if (p == NULL)
deal_with_it();
spin_lock(&p->lock);