diff options
author | Stefan Metzmacher <metze@samba.org> | 2025-08-27 15:54:35 +0200 |
---|---|---|
committer | Steve French <stfrench@microsoft.com> | 2025-09-28 18:29:54 -0500 |
commit | 8aa23bae607e3bd5ced892afc26bfbe8945f531b (patch) | |
tree | 539aa404cadaaff2dc5767d53d8e8ea1c3d92a0f /net/unix/af_unix.c | |
parent | 0491f26f8980d7a4028d3528df09e23f5a64adbe (diff) |
smb: server: make consitent use of spin_lock_irq{save,restore}() in transport_rdma.c
There is a mix of using spin_lock() and spin_lock_irq(), which
is confusing as IB_POLL_WORKQUEUE is used and no code would
be called from any interrupt. So using spin_lock() or even
mutexes would be ok.
But we'll soon share common code with the client, which uses
IB_POLL_SOFTIRQ.
And Documentation/kernel-hacking/locking.rst section
"Cheat Sheet For Locking" says:
- Otherwise (== data can be touched in an interrupt), use
spin_lock_irqsave() and
spin_unlock_irqrestore().
So in order to keep it simple and safe we use that version
now. It will help merging functions into common code and
have consistent locking in all cases.
Acked-by: Namjae Jeon <linkinjeon@kernel.org>
Cc: Steve French <smfrench@gmail.com>
Cc: Tom Talpey <tom@talpey.com>
Cc: linux-cifs@vger.kernel.org
Cc: samba-technical@lists.samba.org
Signed-off-by: Stefan Metzmacher <metze@samba.org>
Signed-off-by: Steve French <stfrench@microsoft.com>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions