From: patchwork-bot+chrome-platform@kernel.org
To: yguoaz <yguoaz@gmail.com>
Cc: tzungbi@kernel.org, jic23@kernel.org, lars@metafoo.de,
bleung@chromium.org, groeck@google.com, dianders@chromium.org,
mazziesaccount@gmail.com, gwendal@chromium.org,
linux-iio@vger.kernel.org, chrome-platform@lists.linux.dev
Subject: Re: [PATCH v3] iio: cros_ec: Fix the allocation size for cros_ec_command
Date: Mon, 11 Sep 2023 04:49:00 +0000 [thread overview]
Message-ID: <169440774012.22573.2546469868468555437.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230630143719.1513906-1-yguoaz@gmail.com>
Hello:
This patch was applied to chrome-platform/linux.git (for-next)
by Jonathan Cameron <Jonathan.Cameron@huawei.com>:
On Fri, 30 Jun 2023 22:37:19 +0800 you wrote:
> The struct cros_ec_command contains several integer fields and a
> trailing array. An allocation size neglecting the integer fields can
> lead to buffer overrun.
>
> Reviewed-by: Tzung-Bi Shih <tzungbi@kernel.org>
> Signed-off-by: Yiyuan Guo <yguoaz@gmail.com>
>
> [...]
Here is the summary with links:
- [v3] iio: cros_ec: Fix the allocation size for cros_ec_command
https://git.kernel.org/chrome-platform/c/8a4629055ef5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-09-11 4:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 14:37 [PATCH v3] iio: cros_ec: Fix the allocation size for cros_ec_command Yiyuan Guo
2023-07-16 13:10 ` Jonathan Cameron
2023-07-16 13:55 ` yguoaz
2023-07-17 3:09 ` Tzung-Bi Shih
2023-07-18 9:37 ` Jonathan Cameron
2023-07-29 11:21 ` Jonathan Cameron
2023-09-11 4:31 ` patchwork-bot+chrome-platform
2023-09-11 4:49 ` patchwork-bot+chrome-platform [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-30 7:36 [PATCH v2] " Tzung-Bi Shih
2023-06-30 8:31 ` [PATCH v3] " Yiyuan Guo
2023-06-30 14:06 ` Guenter Roeck
2023-06-30 14:42 ` yguoaz
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=169440774012.22573.2546469868468555437.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=dianders@chromium.org \
--cc=groeck@google.com \
--cc=gwendal@chromium.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=tzungbi@kernel.org \
--cc=yguoaz@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.