From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <kent.overstreet@linux.dev>
Cc: <boqun.feng@gmail.com>, <linux-fsdevel@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<peterz@infradead.org>, <kuniyu@amazon.com>
Subject: Re: [PATCH 3/4] net: Convert sk->sk_peer_lock to lock_set_cmp_fn_ptr_order()
Date: Sun, 28 Jan 2024 01:17:58 -0800 [thread overview]
Message-ID: <20240128091758.9206-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20240127020833.487907-4-kent.overstreet@linux.dev>
From: Kent Overstreet <kent.overstreet@linux.dev>
Date: Fri, 26 Jan 2024 21:08:30 -0500
> Cc: netdev@vger.kernel.org
> Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
> ---
> net/core/sock.c | 1 +
> net/unix/af_unix.c | 4 ++--
> 2 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/net/core/sock.c b/net/core/sock.c
> index 158dbdebce6a..da7360c0f454 100644
> --- a/net/core/sock.c
> +++ b/net/core/sock.c
> @@ -3474,6 +3474,7 @@ void sock_init_data_uid(struct socket *sock, struct sock *sk, kuid_t uid)
> sk->sk_peer_pid = NULL;
> sk->sk_peer_cred = NULL;
> spin_lock_init(&sk->sk_peer_lock);
> + lock_set_cmp_fn_ptr_order(&sk->sk_peer_lock);
>
> sk->sk_write_pending = 0;
> sk->sk_rcvlowat = 1;
> diff --git a/net/unix/af_unix.c b/net/unix/af_unix.c
> index ac1f2bc18fc9..d013de3c5490 100644
> --- a/net/unix/af_unix.c
> +++ b/net/unix/af_unix.c
> @@ -706,10 +706,10 @@ static void copy_peercred(struct sock *sk, struct sock *peersk)
>
> if (sk < peersk) {
> spin_lock(&sk->sk_peer_lock);
> - spin_lock_nested(&peersk->sk_peer_lock, SINGLE_DEPTH_NESTING);
> + spin_lock(&peersk->sk_peer_lock);
> } else {
> spin_lock(&peersk->sk_peer_lock);
> - spin_lock_nested(&sk->sk_peer_lock, SINGLE_DEPTH_NESTING);
> + spin_lock(&sk->sk_peer_lock);
> }
hmm.. I think we need not hold two locks here in the first place.
Let me post patches.
Thanks!
> old_pid = sk->sk_peer_pid;
> old_cred = sk->sk_peer_cred;
> --
> 2.43.0
next prev parent reply other threads:[~2024-01-28 9:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-27 2:08 [PATCH 0/4] lockdep cmp fn conversions Kent Overstreet
2024-01-27 2:08 ` [PATCH 1/4] fs/pipe: Convert to lockdep_cmp_fn Kent Overstreet
2024-02-02 12:03 ` Jan Kara
2024-02-02 12:25 ` Sedat Dilek
2024-02-05 9:53 ` Jan Kara
2024-02-05 9:59 ` Sedat Dilek
2024-02-02 12:47 ` Kent Overstreet
2024-02-05 10:09 ` Jan Kara
2024-01-27 2:08 ` [PATCH 2/4] pktcdvd: kill mutex_lock_nested() usage Kent Overstreet
2024-01-28 4:29 ` kernel test robot
2024-01-28 6:48 ` kernel test robot
2024-01-27 2:08 ` [PATCH 3/4] net: Convert sk->sk_peer_lock to lock_set_cmp_fn_ptr_order() Kent Overstreet
2024-01-28 9:17 ` Kuniyuki Iwashima [this message]
2024-01-27 2:08 ` [PATCH 4/4] af_unix: convert to lock_cmp_fn Kent Overstreet
2024-01-28 8:28 ` Kuniyuki Iwashima
2024-01-28 19:38 ` Kent Overstreet
2024-01-28 20:56 ` Kuniyuki Iwashima
2024-01-29 1:34 ` Kent Overstreet
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=20240128091758.9206-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=boqun.feng@gmail.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).