From: Badari Pulavarty <pbadari@us.ibm.com>
To: Andrew Morton <akpm@digeo.com>,
Alistair Strachan <alistair@devzero.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.67-mm1
Date: Tue, 8 Apr 2003 16:24:19 -0700 [thread overview]
Message-ID: <200304081624.19444.pbadari@us.ibm.com> (raw)
In-Reply-To: <20030408142853.74709a82.akpm@digeo.com>
[-- Attachment #1: Type: text/plain, Size: 816 bytes --]
On Tuesday 08 April 2003 02:28 pm, Andrew Morton wrote:
> Alistair Strachan <alistair@devzero.co.uk> wrote:
> > On attempting to boot this kernel, I get the following just before init:
> > Kernel panic: VFS: Unable to mount root fs on 03:05
> >
> > 2.5.67 base works fine. I discovered that reverting the following
> > patches allows me to boot. I can increase the granularity of my search
> > if nothing comes immediately to mind:
> >
> > aggregated-disk-stats.patch
> > dynamic-hd_struct-allocation-fixes.patch
> > dynamic-hd_struct-allocation.patch
>
> Ah, good detective work, thanks. It looks like the hd_struct dynamic
> allocation patch has broken devfs partition discovery somehow.
Okay !! My bad.
Here is the patch for 2.5.67-mm1. Could you try and let me know ?
Thanks,
Badari
[-- Attachment #2: devfs.patch --]
[-- Type: text/x-diff, Size: 1098 bytes --]
--- linux-2.5.67/fs/partitions/check.c Tue Apr 8 16:21:30 2003
+++ linux-2.5.67.new/fs/partitions/check.c Tue Apr 8 16:26:01 2003
@@ -163,13 +163,13 @@ static void devfs_register_partition(str
struct hd_struct *p = dev->part;
char devname[16];
- if (p[part-1].de)
+ if (p[part-1]->de)
return;
dir = dev->de;
if (!dir)
return;
sprintf(devname, "part%d", part);
- p[part-1].de = devfs_register (dir, devname, 0,
+ p[part-1]->de = devfs_register (dir, devname, 0,
dev->major, dev->first_minor + part,
S_IFBLK | S_IRUSR | S_IWUSR,
dev->fops, NULL);
@@ -281,14 +281,13 @@ void add_partition(struct gendisk *disk,
memset(p, 0, sizeof(struct hd_struct));
p->start_sect = start;
p->nr_sects = len;
+ p->partno = part;
+ disk->part[part-1] = p;
devfs_register_partition(disk, part);
snprintf(p->kobj.name,KOBJ_NAME_LEN,"%s%d",disk->kobj.name,part);
p->kobj.parent = &disk->kobj;
p->kobj.ktype = &ktype_part;
kobject_register(&p->kobj);
-
- p->partno = part;
- disk->part[part-1] = p;
}
static void disk_sysfs_symlinks(struct gendisk *disk)
next prev parent reply other threads:[~2003-04-08 23:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 16:41 2.5.67-mm1 Alistair Strachan
2003-04-08 21:28 ` 2.5.67-mm1 Andrew Morton
2003-04-08 23:06 ` 2.5.67-mm1 Badari Pulavarty
2003-04-09 7:00 ` 2.5.67-mm1 Alistair Strachan
2003-04-09 15:59 ` 2.5.67-mm1 Badari Pulavarty
2003-04-08 23:24 ` Badari Pulavarty [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-08 11:22 2.5.67-mm1 Andrew Morton
2003-04-08 13:01 ` 2.5.67-mm1 William Lee Irwin III
2003-04-08 13:17 ` 2.5.67-mm1 Ed Tomlinson
2003-04-08 15:31 ` 2.5.67-mm1 Randy.Dunlap
2003-04-08 15:39 ` 2.5.67-mm1 Ed Tomlinson
2003-04-08 16:14 ` 2.5.67-mm1 Randy.Dunlap
2003-04-08 16:18 ` 2.5.67-mm1 Ed Tomlinson
2003-04-08 16:10 ` 2.5.67-mm1 Andrew Morton
2003-04-08 16:50 ` 2.5.67-mm1 Ed Tomlinson
2003-04-08 14:08 ` 2.5.67-mm1 William Lee Irwin III
2003-04-08 16:43 ` 2.5.67-mm1 Helge Hafting
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=200304081624.19444.pbadari@us.ibm.com \
--to=pbadari@us.ibm.com \
--cc=akpm@digeo.com \
--cc=alistair@devzero.co.uk \
--cc=linux-kernel@vger.kernel.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