From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752713AbdJ0SWn (ORCPT <rfc822;w@1wt.eu>);
        Fri, 27 Oct 2017 14:22:43 -0400
Received: from Galois.linutronix.de ([146.0.238.70]:35884 "EHLO
        Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752039AbdJ0SWl (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 27 Oct 2017 14:22:41 -0400
Date: Fri, 27 Oct 2017 20:22:32 +0200 (CEST)
From: Thomas Gleixner <tglx@linutronix.de>
To: David Daney <ddaney@caviumnetworks.com>
cc: Abderrahmane Benbachir <abderrahmane.benbachir@polymtl.ca>,
        linux-kernel@vger.kernel.org, mingo@kernel.org,
        akpm@linux-foundation.org, keescook@chromium.org, jeyu@redhat.com,
        rostedt@goodmis.org, mhocko@suse.com, viresh.kumar@linaro.org,
        thomas.lendacky@amd.com
Subject: Re: [PATCH] init/main.c: check for null pointer before calling
 initcall
In-Reply-To: <7fc6e471-3ff9-83ea-f0c8-638959395494@caviumnetworks.com>
Message-ID: <alpine.DEB.2.20.1710272021210.1922@nanos>
References: <1509122847.11787.5.camel@polymtl.ca> <7fc6e471-3ff9-83ea-f0c8-638959395494@caviumnetworks.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
X-Linutronix-Spam-Score: -1.0
X-Linutronix-Spam-Level: -
X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required,  ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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.