[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<174610863349.2990404.8599127748454819839.git-patchwork-notify@kernel.org>
Date: Thu, 01 May 2025 14:10:33 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Shiming Cheng <shiming.cheng@...iatek.com>
Cc: edumazet@...gle.com, davem@...emloft.net, dsahern@...nel.org,
kuba@...nel.org, pabeni@...hat.com, horms@...nel.org, matthias.bgg@...il.com,
angelogioacchino.delregno@...labora.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, lena.wang@...iatek.com,
jibin.zhang@...iatek.com
Subject: Re: [PATCH v3] net: use sock_gen_put() when sk_state is TCP_TIME_WAIT
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Tue, 29 Apr 2025 09:59:48 +0800 you wrote:
> From: Jibin Zhang <jibin.zhang@...iatek.com>
>
> It is possible for a pointer of type struct inet_timewait_sock to be
> returned from the functions __inet_lookup_established() and
> __inet6_lookup_established(). This can cause a crash when the
> returned pointer is of type struct inet_timewait_sock and
> sock_put() is called on it. The following is a crash call stack that
> shows sk->sk_wmem_alloc being accessed in sk_free() during the call to
> sock_put() on a struct inet_timewait_sock pointer. To avoid this issue,
> use sock_gen_put() instead of sock_put() when sk->sk_state
> is TCP_TIME_WAIT.
>
> [...]
Here is the summary with links:
- [v3] net: use sock_gen_put() when sk_state is TCP_TIME_WAIT
https://git.kernel.org/netdev/net/c/f920436a4429
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