mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maneesh Soni <maneesh@in.ibm.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>, Greg KH <gregkh@us.ibm.com>
Subject: Re: 2.6.10-mm1 panic in sysfs ?
Date: Thu, 6 Jan 2005 13:55:42 +0530	[thread overview]
Message-ID: <20050106082542.GA15246@in.ibm.com> (raw)
In-Reply-To: <1104946602.4000.22.camel@dyn318077bld.beaverton.ibm.com>

On Wed, Jan 05, 2005 at 09:36:42AM -0800, Badari Pulavarty wrote:
> Hi Andrew,
> 
> I get a panic in sysfs_readdir() while booting 2.6.10-mm1
> kernel. Known fixes ?
> 
> Thanks,
> Badari
> 
> 

[....]
> Creating /var/log/boot.msg                                           done
> showconsole: Warning: the ioctl TIOCGDEV is not known by the kernel
> System Boot Control: The system has been                             set up
> Skipped features:                                  boot.cycle boot.sched
> System Boot Control: Running /etc/init.d/boot.local                  done
> INIT: Entering runlevel: 1
> Boot logging started on /dev/ttyS0(/dev/console) at Wed Jan  5 00:33:53 2005
> Master Resource Control: previous runlevel: N, switching to runlevel:1
> Hotplug is already active  (disable with  NOHOTPLUG=1 at the boot prodone
> coldplug scanning input: ***                                         done
>          scanning pci: ****.W*.*..*Unable to handle kernel NULL pointer dereference at virtual address 00000020
>  printing eip:
> c109c8ef
> *pde = 0191c001
> Oops: 0000 [#1]
> SMP
> Modules linked in:
> CPU:    2
> EIP:    0060:[<c109c8ef>]    Not tainted VLI
> EFLAGS: 00010282   (2.6.10-mm1kexec)
> EIP is at sysfs_readdir+0xef/0x280
> eax: 00000000   ebx: c15e1160   ecx: 0000000c   edx: 00000020
> esi: c15e1164   edi: c15dd72d   ebp: c1a7df78   esp: c1a7df3c
> ds: 007b   es: 007b   ss: 0068
> Process getcfg (pid: 1927, threadinfo=c1a7c000 task=c2ba3040)


I think it crashed as the dentry->d_inode is NULL, which is surprising. Getting
some info on the file in process will certainly help. 

--------
static int sysfs_readdir(struct file * filp, void * dirent, filldir_t filldir)
{
        struct dentry *dentry = filp->f_dentry;
        struct sysfs_dirent * parent_sd = dentry->d_fsdata;
        struct sysfs_dirent *cursor = filp->private_data;
        struct list_head *p, *q = &cursor->s_sibling;
        ino_t ino;
        int i = filp->f_pos;
                                                                                
        switch (i) {
                case 0:
                        ino = dentry->d_inode->i_ino;
			^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

                        if (filldir(dirent, ".", 1, i, ino, DT_DIR) < 0)
                                break;
                        filp->f_pos++;
                        i++;

-------

BTW, is this a kexec boot or normal boot? I don't know if this has any 
effect or not but just trying to find reasons behind messages like 
entering runlevel 1 etc..

Thanks
Maneesh


-- 
Maneesh Soni
Linux Technology Center, 
IBM India Software Labs,
Bangalore, India
email: maneesh@in.ibm.com
Phone: 91-80-25044990

      parent reply	other threads:[~2005-01-06 11:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-05 17:36 Badari Pulavarty
2005-01-06  0:52 ` Andrew Morton
2005-01-06  0:39   ` Badari Pulavarty
2005-01-06  8:25 ` Maneesh Soni [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=20050106082542.GA15246@in.ibm.com \
    --to=maneesh@in.ibm.com \
    --cc=akpm@osdl.org \
    --cc=gregkh@us.ibm.com \
    --cc=pbadari@us.ibm.com \
    /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

Powered by JetHome