linux-kernel - [PATCH 0/4] clk: Rate range improvements

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20221018-clk-range-checks-fixes-v1-0-f3ef80518140@cerno.tech>
Date:   Tue, 18 Oct 2022 15:52:55 +0200
From:   Maxime Ripard <maxime@...no.tech>
To:     Stephen Boyd <sboyd@...nel.org>,
        Michael Turquette <mturquette@...libre.com>
Cc:     linux-kernel@...r.kernel.org,
        AngeloGioacchino Del Regno 
        <angelogioacchino.delregno@...labora.com>,
        Maxime Ripard <maxime@...no.tech>, linux-clk@...r.kernel.org
Subject: [PATCH 0/4] clk: Rate range improvements

Hi,

Here's a bunch of patches for issues I came across while debugging the bug
reported by Angelo.

The most important one is the first one. Even though it looks innoculous, it
fixes the bug in question for some reason.

Let me know what you think,
Maxime

To: Michael Turquette <mturquette@...libre.com>
To: Stephen Boyd <sboyd@...nel.org>
Cc: linux-clk@...r.kernel.org
Cc: linux-kernel@...r.kernel.org
Cc: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
Signed-off-by: Maxime Ripard <maxime@...no.tech>

---
Maxime Ripard (4):
      clk: Remove WARN_ON NULL parent in clk_core_init_rate_req()
      clk: Initialize the clk_rate_request even if clk_core is NULL
      clk: Initialize max_rate in struct clk_rate_request
      clk: Warn if we register a mux without determine_rate

 drivers/clk/clk.c | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)
---
base-commit: 56e8142dda103af35e1a47e560517dce355ac001
change-id: 20221018-clk-range-checks-fixes-2039f3523240

Best regards,
-- 
Maxime Ripard <maxime@...no.tech>