From: "Gustavo A. R. Silva" <gustavoars@kernel.org>
To: Dinh Nguyen <dinguyen@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
linux-hardening@vger.kernel.org, linux-clk@vger.kernel.org
Subject: [PATCH v3 0/2][next] clk: socfpga: Fix undefined behavior bug and add bounds-checking coverage
Date: Mon, 23 Oct 2023 21:30:03 -0600 [thread overview]
Message-ID: <cover.1698117815.git.gustavoars@kernel.org> (raw)
This series aims to fix an undefined behavior bug in
`struct stratix10_clock_data` and add bounds-checking
coverage at run-time for flexible-array member `hws`
in `struct clk_hw_onecell_data` when accessed throught
`struct stratix10_clock_data`.
Changes in v3:
- None, really. Just Cc linux-clk@vger.kernel.org this time.
Changes in v2:
- Mention -Wflex-array-member-not-at-end in the changelog text.
- Link: https://lore.kernel.org/linux-hardening/cover.1697493574.git.gustavoars@kernel.org/
v1:
- Link: https://lore.kernel.org/linux-hardening/cover.1697059539.git.gustavoars@kernel.org/
Gustavo A. R. Silva (2):
clk: socfpga: Fix undefined behavior bug in struct
stratix10_clock_data
clk: socfpga: agilex: Add bounds-checking coverage for struct
stratix10_clock_data
drivers/clk/socfpga/clk-agilex.c | 12 ++++++------
drivers/clk/socfpga/clk-s10.c | 6 +++---
drivers/clk/socfpga/stratix10-clk.h | 4 +++-
3 files changed, 12 insertions(+), 10 deletions(-)
--
2.34.1
next reply other threads:[~2023-10-24 3:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 3:30 Gustavo A. R. Silva [this message]
2023-10-24 3:30 ` [PATCH v3 1/2][next] clk: socfpga: Fix undefined behavior bug in struct stratix10_clock_data Gustavo A. R. Silva
2023-10-24 3:31 ` [PATCH v3 2/2][next] clk: socfpga: agilex: Add bounds-checking coverage for " Gustavo A. R. Silva
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=cover.1698117815.git.gustavoars@kernel.org \
--to=gustavoars@kernel.org \
--cc=dinguyen@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
/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