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: <f3c9ba97-2058-a315-d00a-b2fb159cb888@web.de>
Date:   Sat, 28 Dec 2019 16:40:21 +0100
From:   Markus Elfring <Markus.Elfring@....de>
To:     Stephen Boyd <sboyd@...nel.org>,
        Michael Turquette <mturquette@...libre.com>,
        linux-clk@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org,
        Günter Röck <linux@...ck-us.net>,
        Jerome Brunet <jbrunet@...libre.com>
Subject: Re: [PATCH] clk: Warn about critical clks that fail to enable

> If we don't warn here users of the CLK_IS_CRITICAL flag may not know
> that their clk isn't actually enabled because it silently fails to
> enable. Let's drop a big WARN_ON in that case so developers find these
> problems faster.

Would you like to avoid an extra warning for failures with non-critical clocks?


> I suspect that this may start warning for other users.

Will this software development concern trigger any further collateral evolution?

Regards,
Markus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ