From: Tom Herbert <tom@quantonium.net>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, dvyukov@google.com,
john.fastabend@gmail.com, rohit@quantonium.net,
Tom Herbert <tom@quantonium.net>
Subject: [PATCH net-next 3/4] sock_lock: Add try_sock_lock
Date: Fri, 22 Dec 2017 11:47:54 -0800 [thread overview]
Message-ID: <20171222194755.8544-4-tom@quantonium.net> (raw)
In-Reply-To: <20171222194755.8544-1-tom@quantonium.net>
try_sock lock is an opportunistic attempt to acquire a socket lock
without blocking or sleeping. If the socket lock is acquired then
true is returned, else false is returned.
Signed-off-by: Tom Herbert <tom@quantonium.net>
---
include/net/sock.h | 7 +++++++
net/core/sock.c | 20 ++++++++++++++++++++
2 files changed, 27 insertions(+)
diff --git a/include/net/sock.h b/include/net/sock.h
index 3b4ca2046f8c..69fdd1a89591 100644
--- a/include/net/sock.h
+++ b/include/net/sock.h
@@ -1462,6 +1462,13 @@ static inline void lock_sock(struct sock *sk)
lock_sock_nested(sk, 0);
}
+bool try_lock_sock_nested(struct sock *sk, int subclass);
+
+static inline bool try_lock_sock(struct sock *sk)
+{
+ return try_lock_sock_nested(sk, 0);
+}
+
void release_sock(struct sock *sk);
/* BH context may only use the following locking interface. */
diff --git a/net/core/sock.c b/net/core/sock.c
index 72d14b221784..40fb772e2d52 100644
--- a/net/core/sock.c
+++ b/net/core/sock.c
@@ -2782,6 +2782,26 @@ void lock_sock_nested(struct sock *sk, int subclass)
}
EXPORT_SYMBOL(lock_sock_nested);
+bool try_lock_sock_nested(struct sock *sk, int subclass)
+{
+ spin_lock_bh(&sk->sk_lock.slock);
+ if (sk->sk_lock.owned) {
+ spin_unlock_bh(&sk->sk_lock.slock);
+ return false;
+ }
+
+ sk->sk_lock.owned = 1;
+ spin_unlock(&sk->sk_lock.slock);
+
+ /* The sk_lock has mutex_lock() semantics here: */
+
+ mutex_acquire(&sk->sk_lock.dep_map, subclass, 0, _RET_IP_);
+ local_bh_enable();
+
+ return true;
+}
+EXPORT_SYMBOL(try_lock_sock_nested);
+
void release_sock(struct sock *sk)
{
spin_lock_bh(&sk->sk_lock.slock);
--
2.11.0
next prev parent reply other threads:[~2017-12-22 19:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 19:47 [PATCH net-next 0/4] kcm: Fix two locking issues Tom Herbert
2017-12-22 19:47 ` [PATCH net-next 1/4] sock: Add sock_owned_by_user_nocheck Tom Herbert
2017-12-22 19:47 ` [PATCH net-next 2/4] strparser: Call sock_owned_by_user_nocheck Tom Herbert
2017-12-22 19:47 ` Tom Herbert [this message]
2017-12-22 19:47 ` [PATCH net-next 4/4] kcm: Address deadlock between TX and RX paths Tom Herbert
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=20171222194755.8544-4-tom@quantonium.net \
--to=tom@quantonium.net \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rohit@quantonium.net \
/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).