Messages in this thread | | | Subject | Re: [PATCH] net: sock: tracing: Fix sock_exceed_buf_limit not to dereference stale pointer | From | patchwork-bot+netdevbpf@kernel ... | Date | Fri, 08 Jul 2022 11:10:13 +0000 |
| |
Hello:
This patch was applied to netdev/net.git (master) by David S. Miller <davem@davemloft.net>:
On Wed, 6 Jul 2022 10:50:40 -0400 you wrote: > From: "Steven Rostedt (Google)" <rostedt@goodmis.org> > > The trace event sock_exceed_buf_limit saves the prot->sysctl_mem pointer > and then dereferences it in the TP_printk() portion. This is unsafe as the > TP_printk() portion is executed at the time the buffer is read. That is, > it can be seconds, minutes, days, months, even years later. If the proto > is freed, then this dereference will can also lead to a kernel crash. > > [...]
Here is the summary with links: - net: sock: tracing: Fix sock_exceed_buf_limit not to dereference stale pointer https://git.kernel.org/netdev/net/c/820b8963adae
You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
| |