From: patchwork-bot+chrome-platform@kernel.org
To: Kees Cook <keescook@chromium.org>
Cc: bleung@chromium.org, tzungbi@kernel.org, set_pte_at@outlook.com,
dmitry.torokhov@gmail.com, luzmaximilian@gmail.com,
u.kleine-koenig@pengutronix.de, gregkh@linuxfoundation.org,
jiangjian@cdjrlc.com, chrome-platform@lists.linux.dev,
nathan@kernel.org, ndesaulniers@google.com, trix@redhat.com,
hdegoede@redhat.com, lee@kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] platform/chrome: wilco_ec: Annotate struct ec_event_queue with __counted_by
Date: Mon, 25 Sep 2023 10:16:30 +0000 [thread overview]
Message-ID: <169563699076.31071.3693415146979727291.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230922175146.work.219-kees@kernel.org>
Hello:
This patch was applied to chrome-platform/linux.git (for-next)
by Tzung-Bi Shih <tzungbi@kernel.org>:
On Fri, 22 Sep 2023 10:51:47 -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 checking 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 ec_event_queue.
>
> [...]
Here is the summary with links:
- platform/chrome: wilco_ec: Annotate struct ec_event_queue with __counted_by
https://git.kernel.org/chrome-platform/c/1aa8df90f456
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-09-25 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 17:51 [PATCH] platform/chrome: wilco_ec: Annotate struct ec_event_queue with __counted_by Kees Cook
2023-09-23 16:33 ` Gustavo A. R. Silva
2023-09-25 2:30 ` patchwork-bot+chrome-platform
2023-09-25 10:16 ` patchwork-bot+chrome-platform [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=169563699076.31071.3693415146979727291.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=jiangjian@cdjrlc.com \
--cc=keescook@chromium.org \
--cc=lee@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=luzmaximilian@gmail.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=set_pte_at@outlook.com \
--cc=trix@redhat.com \
--cc=tzungbi@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).