linux-kernel - question about clk_hw_register_fixed

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: <alpine.DEB.2.10.1609200811560.3346@hadrien>
Date:   Tue, 20 Sep 2016 08:15:42 +0200 (CEST)
From:   Julia Lawall <julia.lawall@...6.fr>
To:     mturquette@...libre.com, sboyd@...eaurora.org
cc:     linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: question about clk_hw_register_fixed_factor

Hello,

The function clk_hw_register_fixed_factor from
drivers/clk/clk-fixed-factor.c contains:

struct clk_init_data init;
...
fix->hw.init = &init;
...
hw = &fix->hw;
...
return hw;

It looks like hw would then contain a dangling pointer, to init.  Should
this be nulled out, or does it not matter because it is certain that no
one will look at it anyway?  Or did I miss a null assignment elsewhere?

thanks,
julia