From: patchwork-bot+netdevbpf@kernel•org
To: Kees Cook <keescook@chromium•org>
Cc: rajur@chelsio•com, davem@davemloft•net, edumazet@google•com,
kuba@kernel•org, pabeni@redhat•com, gustavoars@kernel•org,
nathan@kernel•org, ndesaulniers@google•com, trix@redhat•com,
linux-kernel@vger•kernel.org, netdev@vger•kernel.org,
linux-hardening@vger•kernel.org, llvm@lists•linux.dev
Subject: Re: [PATCH 0/5] chelsio: Annotate structs with __counted_by
Date: Wed, 04 Oct 2023 22:50:29 +0000 [thread overview]
Message-ID: <169645982948.18987.9169162380776342631.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230929181042.work.990-kees@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Fri, 29 Sep 2023 11:11:44 -0700 you wrote:
> Hi,
>
> This annotates several chelsio structures with the coming __counted_by
> attribute for bounds checking of flexible arrays at run-time. For more details,
> see commit dd06e72e68bc ("Compiler Attributes: Add __counted_by macro").
>
> Thanks!
>
> [...]
Here is the summary with links:
- [1/5] chelsio/l2t: Annotate struct l2t_data with __counted_by
https://git.kernel.org/netdev/net-next/c/3bbae5f1c651
- [2/5] cxgb4: Annotate struct clip_tbl with __counted_by
https://git.kernel.org/netdev/net-next/c/c3db467b0822
- [3/5] cxgb4: Annotate struct cxgb4_tc_u32_table with __counted_by
https://git.kernel.org/netdev/net-next/c/157c56a4fede
- [4/5] cxgb4: Annotate struct sched_table with __counted_by
https://git.kernel.org/netdev/net-next/c/ceba9725fb45
- [5/5] cxgb4: Annotate struct smt_data with __counted_by
https://git.kernel.org/netdev/net-next/c/1508cb7e0752
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-04 22:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 18:11 [PATCH 0/5] chelsio: Annotate structs with __counted_by Kees Cook
2023-09-29 18:11 ` [PATCH 1/5] chelsio/l2t: Annotate struct l2t_data " Kees Cook
2023-09-30 6:39 ` Christophe JAILLET
2023-10-01 6:33 ` Gustavo A. R. Silva
2023-09-29 18:11 ` [PATCH 2/5] cxgb4: Annotate struct clip_tbl " Kees Cook
2023-10-01 6:35 ` Gustavo A. R. Silva
2023-09-29 18:11 ` [PATCH 3/5] cxgb4: Annotate struct cxgb4_tc_u32_table " Kees Cook
2023-10-01 6:36 ` Gustavo A. R. Silva
2023-09-29 18:11 ` [PATCH 4/5] cxgb4: Annotate struct sched_table " Kees Cook
2023-10-01 6:36 ` Gustavo A. R. Silva
2023-09-29 18:11 ` [PATCH 5/5] cxgb4: Annotate struct smt_data " Kees Cook
2023-10-01 6:37 ` Gustavo A. R. Silva
2023-09-29 19:44 ` [PATCH 0/5] chelsio: Annotate structs " Kees Cook
2023-10-02 18:31 ` Jakub Kicinski
[not found] ` <6a750af0-1de2-3bec-3d52-a4007f3afe92@chelsio.com>
2023-10-06 14:27 ` Jakub Kicinski
2023-10-04 22: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=169645982948.18987.9169162380776342631.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=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=rajur@chelsio$(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