netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kirill Tkhai <tkhai@ya.ru>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, kuniyu@amazon.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2] unix: Improve locking scheme in unix_show_fdinfo()
Date: Mon, 16 Jan 2023 11:30:16 +0000	[thread overview]
Message-ID: <167386861620.7624.707492607828278885.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <c6c7084c-56c7-cd37-befe-df718e080597@ya.ru>

Hello:

This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Sat, 14 Jan 2023 12:35:02 +0300 you wrote:
> After switching to TCP_ESTABLISHED or TCP_LISTEN sk_state, alive SOCK_STREAM
> and SOCK_SEQPACKET sockets can't change it anymore (since commit 3ff8bff704f4
> "unix: Fix race in SOCK_SEQPACKET's unix_dgram_sendmsg()").
> 
> Thus, we do not need to take lock here.
> 
> Signed-off-by: Kirill Tkhai <tkhai@ya.ru>
> 
> [...]

Here is the summary with links:
  - [net-next,v2] unix: Improve locking scheme in unix_show_fdinfo()
    https://git.kernel.org/netdev/net-next/c/b27401a30ee4

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-01-16 11:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-14  9:35 [PATCH net-next v2] unix: Improve locking scheme in unix_show_fdinfo() Kirill Tkhai
2023-01-14  9:59 ` Kuniyuki Iwashima
2023-01-16 11:30 ` patchwork-bot+netdevbpf [this message]

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=167386861620.7624.707492607828278885.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=kuniyu@amazon.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=tkhai@ya.ru \
    /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).