[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id:
<175253880626.4035046.17250819591263209118.git-patchwork-notify@kernel.org>
Date: Tue, 15 Jul 2025 00:20:06 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Kuniyuki Iwashima <kuniyu@...gle.com>
Cc: alibuda@...ux.alibaba.com, dust.li@...ux.alibaba.com,
sidraya@...ux.ibm.com, wenjia@...ux.ibm.com, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
mjambigi@...ux.ibm.com, tonylu@...ux.alibaba.com, guwen@...ux.alibaba.com,
horms@...nel.org, kuni1840@...il.com, netdev@...r.kernel.org,
linux-rdma@...r.kernel.org, linux-s390@...r.kernel.org,
syzbot+40bf00346c3fe40f90f2@...kaller.appspotmail.com,
syzbot+f22031fad6cbe52c70e7@...kaller.appspotmail.com,
syzbot+271fed3ed6f24600c364@...kaller.appspotmail.com
Subject: Re: [PATCH v1 net] smc: Fix various oops due to inet_sock type
confusion.
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Fri, 11 Jul 2025 06:07:52 +0000 you wrote:
> syzbot reported weird splats [0][1] in cipso_v4_sock_setattr() while
> freeing inet_sk(sk)->inet_opt.
>
> The address was freed multiple times even though it was read-only memory.
>
> cipso_v4_sock_setattr() did nothing wrong, and the root cause was type
> confusion.
>
> [...]
Here is the summary with links:
- [v1,net] smc: Fix various oops due to inet_sock type confusion.
https://git.kernel.org/netdev/net/c/60ada4fe644e
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