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: <alpine.DEB.2.20.1710272021210.1922@nanos>
Date:   Fri, 27 Oct 2017 20:22:32 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     David Daney <ddaney@...iumnetworks.com>
cc:     Abderrahmane Benbachir <abderrahmane.benbachir@...ymtl.ca>,
        linux-kernel@...r.kernel.org, mingo@...nel.org,
        akpm@...ux-foundation.org, keescook@...omium.org, jeyu@...hat.com,
        rostedt@...dmis.org, mhocko@...e.com, viresh.kumar@...aro.org,
        thomas.lendacky@....com
Subject: Re: [PATCH] init/main.c: check for null pointer before calling
 initcall

On Fri, 27 Oct 2017, David Daney wrote:

> On 10/27/2017 09:47 AM, Abderrahmane Benbachir wrote:
> > Simple check to prevent kernel panic when initcall does not exit
> 
> Interesting, under what circumstances do you observe the panic?
> 
> It would be best to include this information in the patch changelog.

device_initcall(NULL);

might do that, but then it rightfully crashes on boot.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ