LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jan Engelhardt <jengelh@linux01.gwdg.de>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: dsaxena@plexity.net, linux-kernel@vger.kernel.org
Subject: Re: Modprobe as script breaks initramfs kernel?
Date: Thu, 22 Feb 2007 19:44:47 +0100 (MET)	[thread overview]
Message-ID: <Pine.LNX.4.61.0702221941290.7553@yvahk01.tjqt.qr> (raw)
In-Reply-To: <45DD7EED.7030107@tls.msk.ru>


On Feb 22 2007 14:30, Michael Tokarev wrote:
>Deepak Saxena wrote:
>> We attempted an experiment in cleaning up some modprobe messages during 
>> initramfs bootup when the modules directory is missing by moving modprobe 
>> to modprobe-bin and replacing modprobe with the following simple shell script:
>> 
>> #!/bin/sh
>> # Clean up bootup when modules are not present
>> 
>> if [ -e "/lib/modules/'uname -r'/modules.dep" ] ; then
>> 	/sbin/modprobe-bin $*

The nitpick guide says: `uname -r` and "$@" instead of $*  ;-)

>> else
>> 	exit 0
>> fi
>[]
>> BUG: unable to handle kernel NULL pointer dereference at virtual address 00000014
>[]
>> Trace; c0107737 <sys_pipe+17/60>
>> Trace; c01030d7 <syscall_call+7/b>
>
>This is the same issue I reported much earlier with /sbin/hotplug being a script
>in initrfamfs.  The problem is because pipefs isn't initialized yet at the time
>the script gets called, and causes a NULL-pointer deref.  Obviously you're using
>pipe above.

Btw, has this pipefs issue been adressed (by moving pipefs before initramfs
stage), or something?


Jan
-- 

  reply	other threads:[~2007-02-22 18:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-22  0:33 Deepak Saxena
2007-02-22 11:30 ` Michael Tokarev
2007-02-22 18:44   ` Jan Engelhardt [this message]
2007-02-22 20:52     ` Michael Tokarev
2007-02-23  3:44     ` Deepak Saxena

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=Pine.LNX.4.61.0702221941290.7553@yvahk01.tjqt.qr \
    --to=jengelh@linux01.gwdg.de \
    --cc=dsaxena@plexity.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    --subject='Re: Modprobe as script breaks initramfs kernel?' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).