From: "Luis Claudio R. Goncalves" <lgoncalv@redhat.com>
To: stable-rt <stable-rt@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: [PATCH v5.10-rt] rt: fix build issue in be2net
Date: Thu, 20 Mar 2025 21:09:06 -0300 [thread overview]
Message-ID: <Z9yuIpi8zjrTCkoB@uudg.org> (raw)
While working on v5.10.235-rt128-rc1 I noticed a build problem with
CONFIG_BE2NET enabled. Upon inspection I noticed commit 7cfae8627511
("be2net: fix sleeping while atomic bugs in be_ndo_bridge_getlink"),
from v5.10.235, which contains the following statement:
return spin_unlock_bh(&adapter->mcc_lock);
The compiler complains when trying to expand the macro spin_unlock_bh()
in that context, requiring a fix similar to commit 386242acb15e ("rt: fix
build issue in at_hdmac"). This problem is specific to v5.10-rt.
Fixes: 7cfae8627511 ("be2net: fix sleeping while atomic bugs in be_ndo_bridge_getlink")
Signed-off-by: Luis Claudio R. Goncalves <lgoncalv@redhat.com>
---
Sebastian, Steven, All,
Should I apply this solution in a RT update right after I release
v5.10.235-rt128 or should I backport the definition of rt locking
primitives from a newer PREEMPT_RT patch (say v5.15-rt or v6.1-rt)?
diff --git a/drivers/net/ethernet/emulex/benet/be_cmds.c b/drivers/net/ethernet/emulex/benet/be_cmds.c
index 9812a9a5d033..3068ccd37034 100644
--- a/drivers/net/ethernet/emulex/benet/be_cmds.c
+++ b/drivers/net/ethernet/emulex/benet/be_cmds.c
@@ -875,9 +875,10 @@ static int be_cmd_lock(struct be_adapter *adapter)
/* Must be used only in process context */
static void be_cmd_unlock(struct be_adapter *adapter)
{
- if (use_mcc(adapter))
- return spin_unlock_bh(&adapter->mcc_lock);
- else
+ if (use_mcc(adapter)) {
+ spin_unlock_bh(&adapter->mcc_lock);
+ return;
+ } else
return mutex_unlock(&adapter->mbox_lock);
}
next reply other threads:[~2025-03-21 0:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 0:09 Luis Claudio R. Goncalves [this message]
2025-03-24 8:32 ` [PATCH v5.10-rt] rt: fix build issue in be2net Sebastian Andrzej Siewior
2025-03-24 13:37 ` Luis Claudio R. Goncalves
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=Z9yuIpi8zjrTCkoB@uudg.org \
--to=lgoncalv@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=rostedt@goodmis.org \
--cc=stable-rt@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.