From: Andrew Morton <akpm@osdl.org>
To: Miquel van Smoorenburg <miquels@cistron.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: /dev/root: which approach ? [PATCH]
Date: Wed, 10 Mar 2004 12:01:45 -0800 [thread overview]
Message-ID: <20040310120145.248ae62d.akpm@osdl.org> (raw)
In-Reply-To: <20040310162003.GA25688@cistron.nl>
Miquel van Smoorenburg <miquels@cistron.nl> wrote:
>
> Currently if you boot from a blockdevice with a dynamically
> allocated major number (such as LVM or partitionable raid),
> there is no way to check the root filesystem. The root
> fs is still read-only, so you cannot create a device node
> anywhere to point fsck at.
>
> This was discussed on the linux-raid mailinglist, and I proposed
> (as proof of concept) a simple check in bdget() to see if the
> device is being opened is the /dev/root node and if so redirect
> it to the current root device. This is a 8-line patch, the only
> disadvantage I can think of is that for an open file, inode->i_rdev
> is then different from blockdevice->bd_dev.
The /dev/root alias resolution looks nice to me, which probably means that
it has a fatal flaw.
Is it not possible to create a device node on ramfs or ramdisk and point
fsck at that?
next prev parent reply other threads:[~2004-03-10 19:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 16:20 /dev/root: which approach ? [PATCH] Miquel van Smoorenburg
2004-03-10 20:01 ` Andrew Morton [this message]
2004-03-10 20:18 ` Miquel van Smoorenburg
2004-03-10 20:17 ` Mika Penttilä
2004-03-10 20:52 ` Miquel van Smoorenburg
2004-03-12 8:10 ` H. Peter Anvin
2004-03-10 21:01 ` Chris Wedgwood
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=20040310120145.248ae62d.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron.nl \
/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