mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Julian Taylor <julian.taylor@1und1.de>
To: <patchwork-bot+netdevbpf@kernel.org>,
	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, 14 Aug 2025 14:51:27 +0200	[thread overview]
Message-ID: <9fa0c0ea-9c5d-4039-856f-222486283a3c@1und1.de> (raw)
In-Reply-To: <175392900576.2584771.4406793154439387342.git-patchwork-notify@kernel.org>


On 31.07.25 04:30, patchwork-bot+netdevbpf@kernel.org wrote:
> 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!

hello,
as far as I can tell this patch has not made it to the 6.1 stable tree yet in the 6.1.148 review yet:
https://www.spinics.net/lists/stable/msg866199.html

As this seems to be causing issues in distributions releasing 6.1.147 can this still be added to the next possible stable release?
See following issues in relation to loading audit rules which seems to trigger the fixed bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1111017
https://github.com/amazonlinux/amazon-linux-2023/issues/988

I have tested this patch solves the problem in the Debian bookworm using 6.1.x

cheers,
Julian Taylor

  reply	other threads:[~2025-08-14 12:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28  8:06 Fedor Pchelkin
2025-07-28 16:29 ` Kuniyuki Iwashima
2025-07-31  2:30 ` patchwork-bot+netdevbpf
2025-08-14 12:51   ` Julian Taylor [this message]
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=9fa0c0ea-9c5d-4039-856f-222486283a3c@1und1.de \
    --to=julian.taylor@1und1.de \
    --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=patchwork-bot+netdevbpf@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®