All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: linux-clk@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
	"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Subject: [PATCH 0/4] clk drivers: Terminate clk_div_table with sentinel element
Date: Sat, 29 Jan 2022 00:09:18 +0100	[thread overview]
Message-ID: <20220128230922.2047140-1-j.neuschaefer@gmx.net> (raw)

I noticed that some of the clk_div_tables in different drivers are not
terminated with a sentinel element. This may cause the code in
clk-divider.c to read garbage that happens to be beyond the end.

This patchset fixed all instances of this bug that I could find, except
for a case in drivers/phy/ti/phy-j721e-wiz.c that is already fixed in
linux-next:
  https://lore.kernel.org/lkml/20220117110108.4117-1-kishon@ti.com/

Jonathan Neuschäfer (4):
  clk: actions: Terminate clk_div_table with sentinel element
  clk: loongson1: Terminate clk_div_table with sentinel element
  clk: hisilicon: Terminate clk_div_table with sentinel element
  clk: clps711x: Terminate clk_div_table with sentinel element

 drivers/clk/actions/owl-s700.c         | 1 +
 drivers/clk/actions/owl-s900.c         | 4 ++--
 drivers/clk/clk-clps711x.c             | 2 ++
 drivers/clk/hisilicon/clk-hi3559a.c    | 4 ++--
 drivers/clk/loongson1/clk-loongson1c.c | 1 +
 5 files changed, 8 insertions(+), 4 deletions(-)

--
2.34.1


             reply	other threads:[~2022-01-28 23:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28 23:09 Jonathan Neuschäfer [this message]
2022-01-28 23:09 ` [PATCH 1/4] clk: actions: Terminate clk_div_table with sentinel element Jonathan Neuschäfer
2022-01-28 23:09   ` Jonathan Neuschäfer
2022-01-28 23:09 ` [PATCH 2/4] clk: loongson1: " Jonathan Neuschäfer
2022-02-01 13:57   ` Philippe Mathieu-Daudé
2022-02-01 19:43     ` Jonathan Neuschäfer
2022-01-28 23:09 ` [PATCH 3/4] clk: hisilicon: " Jonathan Neuschäfer
2022-01-28 23:09 ` [PATCH 4/4] clk: clps711x: " Jonathan Neuschäfer
2022-01-28 23:09   ` Jonathan Neuschäfer

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=20220128230922.2047140-1-j.neuschaefer@gmx.net \
    --to=j.neuschaefer@gmx.net \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.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 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.