linux-kernel - RE: [PATCH] power/hibernate: Make passing hibernate offsets more friendly

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 26 Mar 2018 07:17:22 +0000
From:   <Mario.Limonciello@...l.com>
To:     <rjw@...ysocki.net>
CC:     <linux-acpi@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] power/hibernate: Make passing hibernate offsets more
 friendly

> -----Original Message-----
> From: Rafael J. Wysocki [mailto:rjw@...ysocki.net]
> Sent: Monday, March 19, 2018 5:11 AM
> To: Limonciello, Mario <Mario_Limonciello@...l.com>
> Cc: linux-acpi@...r.kernel.org; LKML <linux-kernel@...r.kernel.org>
> Subject: Re: [PATCH] power/hibernate: Make passing hibernate offsets more friendly
> 
> On Tuesday, March 6, 2018 11:53:40 AM CET Mario Limonciello wrote:
> > Currently the only way to specify a hibernate offset for a
> > swap file is on the kernel command line.
> >
> > Add a new /sys/power/disk_offset that lets userspace
> > specify the offset and disk to use when initiating a hibernate
> > cycle.
> >
> > Also split up the parsing routine to re-use the same code
> > for the /sys/power/resume and /sys/power/disk_offset parsing.
> >
> > Signed-off-by: Mario Limonciello <mario.limonciello@...l.com>
> 
> Well, IMO /sys/power/resume and /sys/power/disk_offset would be confusingly
> similar after this patch.

Yeah they do function pretty similarly.

> 
> I wonder if adding a resume_offset sysfs attr to simply allow the value of
> resume offset alone to be passed to the kernel at run time (in addition to
> the command line) would work?
> 
> Thanks!

I guess what's your expected flow for how the disk gets selected though?  Should
the kernel be "guessing" which disk to use?

Or should userspace be setting offset via /sys/power/resume_offset followed by
disk in /sys/power/resume (which will show an error in syslog about no partition
found)

If the latter, then I'd like to also modify the behavior to downgrade that missing
hibernate partition to debug instead too.