public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Christian.Gromm@microchip.com
Cc: devel@driverdev.osuosl.org, lkp@lists.01.org,
	linux-kernel@vger.kernel.org
Subject: Re: b276527539 ("staging: most: move core files out of the staging .."): [   12.247349] BUG: kernel NULL pointer dereference, address: 00000000
Date: Fri, 24 Apr 2020 12:55:16 +0200	[thread overview]
Message-ID: <20200424105516.GA395057@kroah.com> (raw)
In-Reply-To: <210f5dac5fe26fba008068a932e51a9cde142c89.camel@microchip.com>

On Fri, Apr 24, 2020 at 10:21:05AM +0000, Christian.Gromm@microchip.com wrote:
> On Fri, 2020-04-24 at 12:16 +0200, Greg KH wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you
> > know the content is safe
> > 
> > On Fri, Apr 24, 2020 at 09:41:36AM +0000, 
> > Christian.Gromm@microchip.com wrote:
> > > On Sun, 2020-03-29 at 21:39 +0800, kernel test robot wrote:
> > > > EXTERNAL EMAIL: Do not click links or open attachments unless you
> > > > know the content is safe
> > > > 
> > > > Greetings,
> > > > 
> > > > 0day kernel testing robot got the below dmesg and the first bad
> > > > commit is
> > > > 
> > > > https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
> > > > staging-next
> > > > 
> > > > commit b276527539188f1f61c082ebef27803db93e536d
> > > > Author:     Christian Gromm <christian.gromm@microchip.com>
> > > > AuthorDate: Tue Mar 10 14:02:40 2020 +0100
> > > > Commit:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > > CommitDate: Tue Mar 24 13:42:44 2020 +0100
> > > > 
> > > >     staging: most: move core files out of the staging area
> > > > 
> > > >     This patch moves the core module to the /drivers/most
> > > > directory
> > > >     and makes all necessary changes in order to not break the
> > > > build.
> > > > 
> > > >     Signed-off-by: Christian Gromm <christian.gromm@microchip.com
> > > > >
> > > >     Link:
> > > > https://lore.kernel.org/r/1583845362-26707-2-git-send-email-christian.gromm@microchip.com
> > > >     Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org
> > > > >
> > > > 
> > > > 22dd4acc80  Staging: speakup: Add identifier name to function
> > > > declaration arguments.
> > > > b276527539  staging: most: move core files out of the staging
> > > > area
> > > > e681bb287f  staging: vt6656: Use DIV_ROUND_UP macro instead of
> > > > specific code
> > > > +-------------------------------------------------------+------
> > > > ----
> > > > --+------------+------------+
> > > > >                                                       |
> > > > > 22dd4acc80
> > > > > > b276527539 | e681bb287f |
> > > > +-------------------------------------------------------+------
> > > > ----
> > > > --+------------+------------+
> > > > > boot_successes                                        |
> > > > > 26         | 0          | 0          |
> > > > > boot_failures                                         |
> > > > > 8          | 11         | 11         |
> > > > > WARNING:possible_circular_locking_dependency_detected |
> > > > > 8          |            |            |
> > > > > BUG:kernel_NULL_pointer_dereference,address           |
> > > > > 0          | 11         | 11         |
> > > > > Oops:#[##]                                            |
> > > > > 0          | 11         | 11         |
> > > > > EIP:__list_add_valid                                  |
> > > > > 0          | 11         | 11         |
> > > > > Kernel_panic-not_syncing:Fatal_exception              |
> > > > > 0          | 11         | 11         |
> > > > +-------------------------------------------------------+------
> > > > ----
> > > > --+------------+------------+
> > > > 
> > > > If you fix the issue, kindly add following tag
> > > > Reported-by: kernel test robot <lkp@intel.com>
> > > > 
> > > > [   12.242090] no options.
> > > > [   12.245364] FPGA DOWNLOAD --->
> > > > [   12.245723] FPGA image file name: xlinx_fpga_firmware.bit
> > > > [   12.246548] GPIO INIT FAIL!!
> > > > [   12.246995] most_sound: init()
> > > > [   12.247349] BUG: kernel NULL pointer dereference, address:
> > > 
> > > The init order of the modules is wrong in case the driver is
> > > being built in-tree.
> > > 
> > > The init function of module most_sound is called before the
> > > core itself is being initialized.
> > > 
> > > [    5.179189] most_sound: init()
> > > [    5.180205] mostcore: __init()
> > > 
> > > Hence the list used in the core to store and track the
> > > registered components has not been initialized with
> > > INIT_LIST_HEAD(&comp_list) by the time the sound module
> > > tries to register itself with the core.
> > > 
> > > The Kconfig of most_sound, however, has a dependency to
> > > MOST. How can the build system be forced to initialize the
> > > core module first?
> > 
> > Linker order is the thing here.
> > 
> > You can mess with the init levels here, and use subsys_initcall() for
> > mostcore, will that fix it?
> 
> I already gave it a try and it works. But is it ok to use the
> subsys_initcall() function when the driver is being built as a
> module?

Yes, that works the same, see it's use elsewhere in the kernel tree, and
for what it "degrades to" if the file is being built as a module.

thanks,

greg k-h

      reply	other threads:[~2020-04-24 10:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-29 13:39 b276527539 ("staging: most: move core files out of the staging .."): [ 12.247349] BUG: kernel NULL pointer dereference, address: 00000000 kernel test robot
2020-03-31 19:30 ` Christian.Gromm
2020-04-24  9:41 ` Christian.Gromm
2020-04-24 10:16   ` Greg KH
2020-04-24 10:21     ` Christian.Gromm
2020-04-24 10:55       ` Greg KH [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200424105516.GA395057@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Christian.Gromm@microchip.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@lists.01.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox