From: Andrew Morton <akpm@osdl.org>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: psusi@cfl.rr.com, jzb@aexorsyst.com, linux-kernel@vger.kernel.org
Subject: Re: root=/dev/sda1 fails but root=0x0801 works...
Date: Tue, 14 Feb 2006 23:32:56 -0800 [thread overview]
Message-ID: <20060214233256.2969b4b7.akpm@osdl.org> (raw)
In-Reply-To: <20060215071018.GJ27946@ftp.linux.org.uk>
Al Viro <viro@ftp.linux.org.uk> wrote:
>
> On Tue, Feb 14, 2006 at 10:59:50PM -0800, Andrew Morton wrote:
> > Al Viro <viro@ftp.linux.org.uk> wrote:
> > >
> > > Read init/do_mounts.c::name_to_dev_t().
> > >
> >
> > I tried to do that a while ago, when I was trying to use it for
> > name_to_dev_t()ing in swsusp somewhere.
> >
> >
> > >From my notes at the time:
> >
> > a) It barfs if /sys is already mounted.
>
> It's called from late boot code.
>
> > b) Fix that, mkdir and mount barf because it needs set_fs(KERNEL_DS)
>
> It's called from late boot code, running as kernel thread.
Well. I was trying to use it for something else...
> > c) Fix that, it barfs because name_to_dev_t is just broken. It is
> > accessing the wrong pathnames in /sys.
>
> Details, please.
I just don't remember, sorry. From inspection it _looks_ OK. But I do
remember getting -ENOENT, looking at the pathnames and deciding that it was
miles off.
swsusp has a habit of leaving a trailing \n at the end of resume_file, but
it was more than that.
And I threw away the patch which exercised this. Oh well.
(Wonders whether software_resume()'s call to name_to_dev_t() can work and
if so, whether all that stuff as well as name_to_dev_t() can become __init).
next prev parent reply other threads:[~2006-02-15 7:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 7:16 John Z. Bohach
2006-02-14 15:42 ` Phillip Susi
2006-02-14 16:24 ` Al Viro
2006-02-14 17:20 ` John Z. Bohach
2006-02-14 19:03 ` Phillip Susi
2006-02-15 6:59 ` Andrew Morton
2006-02-15 7:10 ` Al Viro
2006-02-15 7:32 ` Andrew Morton [this message]
2006-02-15 7:59 ` Al Viro
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=20060214233256.2969b4b7.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jzb@aexorsyst.com \
--cc=linux-kernel@vger.kernel.org \
--cc=psusi@cfl.rr.com \
--cc=viro@ftp.linux.org.uk \
/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