All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Fedor Pchelkin <pchelkin@ispras.ru>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	kuniyu@google.com, edumazet@google.com, horms@kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	lvc-project@linuxtesting.org, stable@vger.kernel.org
Subject: Re: [PATCH net] netlink: avoid infinite retry looping in netlink_unicast()
Date: Thu, 31 Jul 2025 02:30:05 +0000	[thread overview]
Message-ID: <175392900576.2584771.4406793154439387342.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250728080727.255138-1-pchelkin@ispras.ru>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 28 Jul 2025 11:06:47 +0300 you wrote:
> netlink_attachskb() checks for the socket's read memory allocation
> constraints. Firstly, it has:
> 
>   rmem < READ_ONCE(sk->sk_rcvbuf)
> 
> to check if the just increased rmem value fits into the socket's receive
> buffer. If not, it proceeds and tries to wait for the memory under:
> 
> [...]

Here is the summary with links:
  - [net] netlink: avoid infinite retry looping in netlink_unicast()
    https://git.kernel.org/netdev/net/c/759dfc7d04ba

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



  parent reply	other threads:[~2025-07-31  2:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28  8:06 [PATCH net] netlink: avoid infinite retry looping in netlink_unicast() Fedor Pchelkin
2025-07-28 16:29 ` Kuniyuki Iwashima
2025-07-31  2:30 ` patchwork-bot+netdevbpf [this message]
2025-08-14 12:51   ` Julian Taylor
2025-08-14 13:57     ` Greg KH
2025-08-14 14:14       ` Julian Taylor
2025-08-14 14:21         ` Greg KH

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=175392900576.2584771.4406793154439387342.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lvc-project@linuxtesting.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pchelkin@ispras.ru \
    --cc=stable@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.