From: Amery Hung <ameryhung@gmail.com>
To: bpf@vger.kernel.org
Cc: netdev@vger.kernel.org, alexei.starovoitov@gmail.com,
andrii@kernel.org, daniel@iogearbox.net, memxor@gmail.com,
david.laight.linux@gmail.com, dave@stgolabs.net,
paulmck@kernel.org, josh@joshtriplett.org, ameryhung@gmail.com,
kernel-team@meta.com
Subject: [PATCH bpf-next v2 2/2] rqspinlock: Handle return of raw_res_spin_lock{_irqsave} in locktorture
Date: Fri, 21 Nov 2025 12:57:24 -0800 [thread overview]
Message-ID: <20251121205724.2934650-2-ameryhung@gmail.com> (raw)
In-Reply-To: <20251121205724.2934650-1-ameryhung@gmail.com>
Return errors from raw_res_spin_lock{_irqsave}() to writelock(). This is
simply to silence the unused result warning. lock_torture_writer()
currently does not handle errors returned from writelock(). This aligns
with the existing torture test for ww_mutex.
Signed-off-by: Amery Hung <ameryhung@gmail.com>
---
kernel/locking/locktorture.c | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/kernel/locking/locktorture.c b/kernel/locking/locktorture.c
index ce0362f0a871..2b3686b96907 100644
--- a/kernel/locking/locktorture.c
+++ b/kernel/locking/locktorture.c
@@ -369,8 +369,7 @@ static rqspinlock_t rqspinlock;
static int torture_raw_res_spin_write_lock(int tid __maybe_unused)
{
- raw_res_spin_lock(&rqspinlock);
- return 0;
+ return raw_res_spin_lock(&rqspinlock);
}
static void torture_raw_res_spin_write_unlock(int tid __maybe_unused)
@@ -392,8 +391,12 @@ static struct lock_torture_ops raw_res_spin_lock_ops = {
static int torture_raw_res_spin_write_lock_irq(int tid __maybe_unused)
{
unsigned long flags;
+ int err;
+
+ err = raw_res_spin_lock_irqsave(&rqspinlock, flags);
+ if (err)
+ return err;
- raw_res_spin_lock_irqsave(&rqspinlock, flags);
cxt.cur_ops->flags = flags;
return 0;
}
--
2.47.3
next prev parent reply other threads:[~2025-11-21 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 20:57 [PATCH bpf-next v2 1/2] rqspinlock: Annotate rqspinlock lock acquiring functions with __must_check Amery Hung
2025-11-21 20:57 ` Amery Hung [this message]
2025-11-21 21:27 ` bot+bpf-ci
2025-11-21 21:54 ` Amery Hung
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251121205724.2934650-2-ameryhung@gmail.com \
--to=ameryhung@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dave@stgolabs.net \
--cc=david.laight.linux@gmail.com \
--cc=josh@joshtriplett.org \
--cc=kernel-team@meta.com \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=paulmck@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox