From: Andrew Morton <akpm@osdl.org>
To: Eyal Lebedinsky <eyal@eyal.emu.id.au>
Cc: linux-kernel@vger.kernel.org, Jan Kara <jack@suse.cz>
Subject: Re: 2.6.10-rc2-mm3 - oops on boot
Date: Mon, 22 Nov 2004 15:10:49 -0800 [thread overview]
Message-ID: <20041122151049.6b9dc575.akpm@osdl.org> (raw)
In-Reply-To: <41A26BD4.8000509@eyal.emu.id.au>
Eyal Lebedinsky <eyal@eyal.emu.id.au> wrote:
>
> EIP is at invalidate_bdev+0x10/0x29
> eax: 00000000 ebx: 00000000 ecx: 00000000 edx: f7ca4320
> esi: 00000002 edi: 00000006 ebp: f7cb3400 esp: c194bef8
> ds: 007b es: 007b ss: 0068
> Process swapper (pid: 1, threadinfo=c194b000 task=c194aa80)
> Stack: 00000000 00000004 c0187aa3 00000000 00000000 00000005 00000006 00000006
> 00000000 00000000 00000000 f7cb3400 c1931f80 00000000 c0176377 f7cb3400
> ffffffff c02cc149 00000000 ffffffff c194bf60 c02cc149 00000000 c0176498
> Call Trace:
> [<c0187aa3>] vfs_quota_off+0xc0/0x219
> [<c0176377>] do_umount+0x19e/0x235
> [<c0176498>] sys_umount+0x8a/0x8e
> [<c03c72b0>] umount_devfs+0x17/0x1b
> [<c03c71bd>] prepare_namespace+0x2e/0xd7
> [<c012e2fc>] flush_workqueue+0x77/0x95
> [<c0100454>] init+0x14e/0x18d
> [<c0100306>] init+0x0/0x18d
> [<c010128d>] kernel_thread_helper+0x5/0xb
> Code: 5e 5f 5d c3 89 5c 24 1c f0 ff 43 0c eb d5 0f 0b b2 01 7f 6d 2d c0 e9 4b ff ff ff 83 ec 08 89 5c 24 04 8b 5c 24 0c e8 f5 0f 00 00 <8b> 43 04 8b 5c 24 04 8b 80 b4 00 00 00 89 44 24 0c 83 c4 08 e9
> <0>Kernel panic - not syncing: Attempted to kill init!
Well devfs has a NULL sb->s_bdev, so the oops is no surprise. However I'm
a bit surprised that we even got that far into the quota code.
Maybe it's a bit odd that sync_blockdev() accepts a NULL argument, but
invalidate_bdev() does not. Whatever. This should get you going:
--- 25/fs/dquot.c~vfs_quota_off-oops-fix Mon Nov 22 15:08:31 2004
+++ 25-akpm/fs/dquot.c Mon Nov 22 15:08:49 2004
@@ -1372,7 +1372,8 @@ int vfs_quota_off(struct super_block *sb
mark_inode_dirty(toput[cnt]);
iput(toput[cnt]);
}
- invalidate_bdev(sb->s_bdev, 0);
+ if (sb->s_bdev)
+ invalidate_bdev(sb->s_bdev, 0);
return 0;
}
_
next prev parent reply other threads:[~2004-11-22 23:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 6:39 2.6.10-rc2-mm3 Andrew Morton
2004-11-22 10:26 ` 2.6.10-rc2-mm3 Paul Mackerras
2004-11-22 13:45 ` 2.6.10-rc2-mm3 Adrian Bunk
2004-11-22 15:51 ` [patch] 2.6.10-rc2-mm3: DVB: philips_tdm1316l_config multiple definition Adrian Bunk
2004-11-22 16:09 ` [linux-dvb-maintainer] " Johannes Stezenbach
2004-11-22 17:01 ` Michael Hunold
2004-11-22 22:08 ` dvb-ttpci not smp safe [was: [linux-dvb-maintainer] [patch] 2.6.10-rc2-mm3: DVB: philips_tdm1316l_config multiple definition] syrius.ml
2004-11-22 19:15 ` 2.6.10-rc2-mm3 Chris Ross
2004-11-22 22:44 ` 2.6.10-rc2-mm3 - oops on boot Eyal Lebedinsky
2004-11-22 23:10 ` Andrew Morton [this message]
2004-11-23 0:17 ` Eyal Lebedinsky
2004-11-23 11:41 ` Jan Kara
2004-11-23 12:58 ` Chris Ross
2004-11-23 19:13 ` Chris Ross
2004-11-22 23:56 ` 2.6.10-rc2-mm3 Fabio Coatti
2004-11-23 0:21 ` 2.6.10-rc2-mm3 (oops on AMD64) Rafael J. Wysocki
2004-11-24 16:19 ` 2.6.10-rc2-mm3 William Lee Irwin III
2004-11-24 18:53 ` 2.6.10-rc2-mm3 Tom Rini
2004-11-25 2:31 ` 2.6.10-rc2-mm3 J.A. Magallon
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=20041122151049.6b9dc575.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=eyal@eyal.emu.id.au \
--cc=jack@suse.cz \
--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
all inboxes | Powered by JetHome®