mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: "Nick Piggin" <s3293115@student.anu.edu.au>
Cc: linux-kernel@vger.kernel.org, rgooch@ras.ucalgary.ca
Subject: Re: [2.4.10-pre11 OOPS] in do_generic_file_read
Date: Wed, 19 Sep 2001 18:43:02 +1000 (EST)	[thread overview]
Message-ID: <15272.23190.629095.594202@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <000701c13ffb$785126d0$0200a8c0@W2K>
In-Reply-To: <000701c13ffb$785126d0$0200a8c0@W2K>

Nick Piggin writes:

> I got the following oops on startup while mounting the root filesystem.
> Unfortunately there was no "Code" because of a bad EIP value. If anyone
> would like more information or anything for me to test, please CC me.

I got something similar.  I would predict that you are using devfs.
The problem is that devfs doesn't set inode->i_mapping->a_ops for a
block device.  Ext2 (for instance) calls init_special_inode, and pre11
added a line to that procedure to initialize that field.  But devfs
doesn't use init_special_inode.

The patch below fixes the problem for me.  It may be that devfs should
be calling init_special_inode instead, but that sets inode->i_fop as
well and it looks like devfs sets that a bit differently.  Richard?

Paul.

diff -urN linux/fs/devfs/base.c pmac/fs/devfs/base.c
--- linux/fs/devfs/base.c	Wed Sep 19 16:39:20 2001
+++ pmac/fs/devfs/base.c	Wed Sep 19 17:11:01 2001
@@ -2286,6 +2286,7 @@
 	}
 	else printk ("%s: read_inode(%d): no block device from bdget()\n",
 		     DEVFS_NAME, (int) inode->i_ino);
+	inode->i_mapping->a_ops = &def_blk_aops;
     }
     else if ( S_ISFIFO (de->inode.mode) ) inode->i_fop = &def_fifo_fops;
     else if ( S_ISREG (de->inode.mode) ) inode->i_size = de->u.fcb.u.file.size;

  reply	other threads:[~2001-09-19  8:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-18  4:36 Nick Piggin
2001-09-19  8:43 ` Paul Mackerras [this message]
2001-09-19 16:47 ` Richard Gooch

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=15272.23190.629095.594202@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgooch@ras.ucalgary.ca \
    --cc=s3293115@student.anu.edu.au \
    /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

all inboxes | Powered by JetHome®