Re: [PATCH v3 00/14] Remove redundant rcu_read_lock/unlock() in spin_lock
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Date: 2025-11-18 07:24:53
Also in:
cgroups, intel-gfx, linux-acpi, linux-fsdevel, linux-nfs, linux-rt-devel, linux-s390, linux-security-module, linux-wireless, lkml
On 2025-09-16 12:47:21 [+0800], pengdonglin wrote: Hi,
There is no need no explicitly start a RCU read section if one has already been started implicitly by spin_lock(). Simplify the code and remove the inner rcu_read_lock() invocation.
I'm not going argue if this is a good or not but: If you intend to get this merged I suggest you rebase your series (or what is left since I think a few patches got merged) on top of current tree and resend them individually targeting the relevant tree/ list. Otherwise everyone might think someone else is in charge of this big series. Sebastian