netdev - Re: [PATCH] net: smc: fix spurious error message from __sock

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: 
 <170790842577.10752.4092253084459431280.git-patchwork-notify@kernel.org>
Date: Wed, 14 Feb 2024 11:00:25 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Dmitry Antipov <dmantipov@...dex.ru>
Cc: ubraun@...ux.ibm.com, kgraul@...ux.ibm.com, jaka@...ux.ibm.com,
 davem@...emloft.net, netdev@...r.kernel.org, lvc-project@...uxtesting.org
Subject: Re: [PATCH] net: smc: fix spurious error message from __sock_release()

Hello:

This patch was applied to netdev/net.git (main)
by David S. Miller <davem@...emloft.net>:

On Mon, 12 Feb 2024 17:34:02 +0300 you wrote:
> Commit 67f562e3e147 ("net/smc: transfer fasync_list in case of fallback")
> leaves the socket's fasync list pointer within a container socket as well.
> When the latter is destroyed, '__sock_release()' warns about its non-empty
> fasync list, which is a dangling pointer to previously freed fasync list
> of an underlying TCP socket. Fix this spurious warning by nullifying
> fasync list of a container socket.
> 
> [...]

Here is the summary with links:
  - net: smc: fix spurious error message from __sock_release()
    https://git.kernel.org/netdev/net/c/6cf9ff463317

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