linux-kernel - Re: [PATCH] clk: ti: Don't reference clk_init

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-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20190816145135.82244206C1@mail.kernel.org>
Date:   Fri, 16 Aug 2019 07:51:34 -0700
From:   Stephen Boyd <sboyd@...nel.org>
To:     Michael Turquette <mturquette@...libre.com>,
        Stephen Boyd <sboyd@...nel.org>
Cc:     linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org,
        linux-omap@...r.kernel.org, Tero Kristo <t-kristo@...com>,
        Tony Lindgren <tony@...mide.com>
Subject: Re: [PATCH] clk: ti: Don't reference clk_init_data after registration

Quoting Stephen Boyd (2019-08-15 15:12:49)
> A future patch is going to change semantics of clk_register() so that
> clk_hw::init is guaranteed to be NULL after a clk is registered. Avoid
> referencing this member here so that we don't run into NULL pointer
> exceptions.
> 
> Cc: Tero Kristo <t-kristo@...com>
> Cc: Tony Lindgren <tony@...mide.com>
> Signed-off-by: Stephen Boyd <sboyd@...nel.org>
> ---
> 
> This might be causing boot regressions in linux-next. Not sure.
> 

I don't see linux-next boot regressions in kernel-ci so it must be
working.