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
| ||
|
Message-Id: <169784942469.14403.8655221823473150989.git-patchwork-notify@kernel.org> Date: Sat, 21 Oct 2023 00:50:24 +0000 From: patchwork-bot+netdevbpf@...nel.org To: Eric Dumazet <edumazet@...gle.com> Cc: davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com, soheil@...gle.com, ncardwell@...gle.com, netdev@...r.kernel.org, eric.dumazet@...il.com, shakeelb@...gle.com Subject: Re: [PATCH v2 net] net: do not leave an empty skb in write queue Hello: This patch was applied to netdev/net.git (main) by Jakub Kicinski <kuba@...nel.org>: On Thu, 19 Oct 2023 11:24:57 +0000 you wrote: > Under memory stress conditions, tcp_sendmsg_locked() > might call sk_stream_wait_memory(), thus releasing the socket lock. > > If a fresh skb has been allocated prior to this, > we should not leave it in the write queue otherwise > tcp_write_xmit() could panic. > > [...] Here is the summary with links: - [v2,net] net: do not leave an empty skb in write queue https://git.kernel.org/netdev/net/c/72bf4f1767f0 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists