From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>
Cc: Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Kuniyuki Iwashima <kuniyu@amazon.com>,
"Kuniyuki Iwashima" <kuni1840@gmail.com>,
<netdev@vger.kernel.org>
Subject: [PATCH v1 net-next] checkpatch: Discourage a new use of rtnl_lock() variants.
Date: Tue, 11 Feb 2025 16:04:47 +0900 [thread overview]
Message-ID: <20250211070447.25001-1-kuniyu@amazon.com> (raw)
rtnl_lock() is a "Big Kernel Lock" in the networking slow path
and still serialises most of RTM_(NEW|DEL|SET)* rtnetlink requests.
Commit 76aed95319da ("rtnetlink: Add per-netns RTNL.") started a
very large, in-progress, effort to make the RTNL lock scope per
network namespace.
However, there are still some patches that newly use rtnl_lock(),
which is now discouraged, and we need to revisit it later.
Let's warn about the case by checkpatch.
The target functions are as follows:
* rtnl_lock()
* rtnl_trylock()
* rtnl_lock_interruptible()
* rtnl_lock_killable()
and the warning will be like:
WARNING: A new use of rtnl_lock() variants is discouraged, try to use rtnl_net_lock(net) variants
#18: FILE: net/core/rtnetlink.c:79:
+ rtnl_lock();
Signed-off-by: Kuniyuki Iwashima <kuniyu@amazon.com>
---
It would be nice if this patch goes through net-next.git to catch
new rtnl_lock() users by netdev CI.
---
scripts/checkpatch.pl | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 7b28ad331742..09d5420436cc 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -6995,6 +6995,12 @@ sub process {
# }
# }
+# A new use of rtnl_lock() is discouraged as it's being converted to rtnl_net_lock(net).
+ if ($line =~ /^\+.*\brtnl_(try)?lock(_interruptible|_killable)?\(\)/) {
+ WARN("rtnl_lock()",
+ "A new use of rtnl_lock() variants is discouraged, try to use rtnl_net_lock(net) variants\n" . $herecurr);
+ }
+
# strcpy uses that should likely be strscpy
if ($line =~ /\bstrcpy\s*\(/) {
WARN("STRCPY",
--
2.39.5 (Apple Git-154)
next reply other threads:[~2025-02-11 7:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 7:04 Kuniyuki Iwashima [this message]
2025-02-12 18:23 ` [PATCH v1 net-next] checkpatch: Discourage a new use of rtnl_lock() variants Simon Horman
2025-02-13 11:03 ` Paolo Abeni
2025-02-13 12:10 ` Kuniyuki Iwashima
2025-02-13 12:18 ` Kuniyuki Iwashima
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=20250211070447.25001-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=apw@canonical.com \
--cc=davem@davemloft.net \
--cc=dwaipayanray1@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=joe@perches.com \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=lukas.bulwahn@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).