Re: [PATCH v3 00/14] Remove redundant rcu_read_lock/unlock() in spin_lock
Sebastian Andrzej Siewior <[email protected]>
| Newsgroups | gmane.linux.kernel.aio.general,gmane.linux.kernel,gmane.linux.nfs,gmane.linux.file-systems,gmane.linux.kernel.lsm,gmane.linux.network,gmane.comp.freedesktop.xorg.drivers.intel,gmane.linux.kernel.wireless.general,gmane.linux.acpi.devel,gmane.linux.kernel.cgroups |
|---|---|
| Message-ID | <[email protected]> |
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 -- To unsubscribe, send a message with 'unsubscribe linux-aio' in the body to [email protected]. For more info on Linux AIO, see: http://www.kvack.org/aio/ Don't email: <a href=mailto:"[email protected]">[email protected]</a>