From: Yu Chen <yu.c.chen@intel.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Mike Snitzer <snitzer@redhat.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Linux PM list <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Zhang Rui <rui.zhang@intel.com>
Subject: Re: [RFC V2] init: support device of major:minor:offset format
Date: Thu, 07 May 2015 09:42:27 +0800 [thread overview]
Message-ID: <554AC303.4060007@intel.com> (raw)
In-Reply-To: <CAMuHMdW1PEksGjE7mcKoN_n7sdLorLgw9uiJDxxp469C4ru-SQ@mail.gmail.com>
Hi, Geert
On 05/07/2015 12:49 AM, Geert Uytterhoeven wrote:
> On Wed, May 6, 2015 at 2:24 AM, Chen Yu <yu.c.chen@intel.com> wrote:
>> Distribution like Ubuntu uses klibc rather than uswsusp to resume
>> system from hibernation, which will treat swap partition/file in
>> the form of major:minor:offset. For example, 8:3:0 represents a
>> swap partition in klibc, and klibc's resume process in initrd will
>> finally echo 8:3:0 to /sys/power/resume for manually restoring.
>> However in current implementation, 8:3:0 will be treated as an invalid
>
> Why can't klibc write the same information as uswsusp?
I agree. However it seems that klibc treats all device/file as such
fixed format when dealing with hibernation, I guess that might be
easier for it to implement?
> Why should the kernel adapt to a specific piece of userspace?
>
>> device format, and it is found that manual resumming from hibernation
>> will fail on lastest kernel.
>
> Is this a regression, perhaps introduced by commit 283e7ad024115571
> ("init: stricter checking of major:minor root= values")? If that is the case,
> please say so.
>
yes, it is. I think there's a modified patch for it at:
https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=for-next&id=cb31ef485dd4c6a205d1064b42027f82076d00c8
Thanks
Best Regards,
Yu
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
next prev parent reply other threads:[~2015-05-07 1:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 0:24 [RFC V2] init: support device of major:minor:offset format Chen Yu
2015-05-06 16:49 ` Geert Uytterhoeven
2015-05-07 1:42 ` Yu Chen [this message]
2015-05-07 7:04 ` Geert Uytterhoeven
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=554AC303.4060007@intel.com \
--to=yu.c.chen@intel.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rui.zhang@intel.com \
--cc=snitzer@redhat.com \
/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