From: patchwork-bot+netdevbpf@kernel.org
To: Vlad Buslov <vladbu@nvidia.com>
Cc: davem@davemloft.net, kuba@kernel.org, jhs@mojatatu.com,
jiri@resnulli.us, xiyou.wangcong@gmail.com, saeedm@mellanox.com,
fw@strlen.de, wenxu@ucloud.cn, netdev@vger.kernel.org
Subject: Re: [PATCH net v2] net: zero-initialize tc skb extension on allocation
Date: Tue, 25 May 2021 22:40:09 +0000 [thread overview]
Message-ID: <162198240925.22762.3522660607313028652.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210525132152.2589420-1-vladbu@nvidia.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Tue, 25 May 2021 16:21:52 +0300 you wrote:
> Function skb_ext_add() doesn't initialize created skb extension with any
> value and leaves it up to the user. However, since extension of type
> TC_SKB_EXT originally contained only single value tc_skb_ext->chain its
> users used to just assign the chain value without setting whole extension
> memory to zero first. This assumption changed when TC_SKB_EXT extension was
> extended with additional fields but not all users were updated to
> initialize the new fields which leads to use of uninitialized memory
> afterwards. UBSAN log:
>
> [...]
Here is the summary with links:
- [net,v2] net: zero-initialize tc skb extension on allocation
https://git.kernel.org/netdev/net/c/9453d45ecb6c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-05-25 22:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 13:21 [PATCH net v2] net: zero-initialize tc skb extension on allocation Vlad Buslov
2021-05-25 21:48 ` Cong Wang
2021-05-25 22:40 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=162198240925.22762.3522660607313028652.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=vladbu@nvidia.com \
--cc=wenxu@ucloud.cn \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.