From: patchwork-bot+netdevbpf@kernel•org
To: Kees Cook <keescook@chromium•org>
Cc: davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
pabeni@redhat•com, johannes.berg@intel•com,
netdev@vger•kernel.org, gustavoars@kernel•org, nathan@kernel•org,
ndesaulniers@google•com, trix@redhat•com,
linux-kernel@vger•kernel.org, linux-hardening@vger•kernel.org,
llvm@lists•linux.dev
Subject: Re: [PATCH] netlink: Annotate struct netlink_policy_dump_state with __counted_by
Date: Fri, 06 Oct 2023 09:50:28 +0000 [thread overview]
Message-ID: <169658582861.14501.9894166775052495116.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231003232102.work.430-kees@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft•net>:
On Tue, 3 Oct 2023 16:21:02 -0700 you wrote:
> Prepare for the coming implementation by GCC and Clang of the __counted_by
> attribute. Flexible array members annotated with __counted_by can have
> their accesses bounds-checked at run-time via CONFIG_UBSAN_BOUNDS (for
> array indexing) and CONFIG_FORTIFY_SOURCE (for strcpy/memcpy-family
> functions).
>
> As found with Coccinelle[1], add __counted_by for struct netlink_policy_dump_state.
>
> [...]
Here is the summary with links:
- netlink: Annotate struct netlink_policy_dump_state with __counted_by
https://git.kernel.org/netdev/net-next/c/eaede99c3aeb
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:[~2023-10-06 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 23:21 [PATCH] netlink: Annotate struct netlink_policy_dump_state with __counted_by Kees Cook
2023-10-03 23:40 ` Gustavo A. R. Silva
2023-10-06 9:50 ` 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=169658582861.14501.9894166775052495116.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=gustavoars@kernel$(echo .)org \
--cc=johannes.berg@intel$(echo .)com \
--cc=keescook@chromium$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux-hardening@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=llvm@lists$(echo .)linux.dev \
--cc=nathan@kernel$(echo .)org \
--cc=ndesaulniers@google$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=trix@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox