linux-kernel - Re: [PATCH -mm 5/6] mm: Print first block offset for swap areas

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:	Fri, 22 Sep 2006 00:46:31 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Dave Jones <davej@...hat.com>
Cc:	Pavel Machek <pavel@....cz>, Andrew Morton <akpm@...l.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -mm 5/6] mm: Print first block offset for swap areas

On Friday, 22 September 2006 00:10, Dave Jones wrote:
> On Thu, Sep 21, 2006 at 11:32:53PM +0200, Pavel Machek wrote:
>  > On Wed 2006-09-20 21:54:38, Rafael J. Wysocki wrote:
>  > > In order to use a swap file with swsusp we need to know the offset at which
>  > > its swap header is located.  However, the swap header is always located in the
>  > > first block of the swap file and it's quite easy to make sys_swapon() print
>  > > the offset of the swap file's (or swap partition's) first block.
>  > > 
>  > > Signed-off-by: Rafael J. Wysocki <rjw@...k.pl>
>  > 
>  > ACK.
>  > 
>  > (main point of this is that it changes user-visible printk, but that's
>  > probably okay, and way better than changing /proc files...)
> 
> As a user-interface, "read the number from dmesg that swapon printk'd
> and add that to your boot command line" is pretty damned awful.

Yes, it is.  However, the only solution I've invented so far is to print
that number in /proc/swaps, but that would be changing the
kernel-user interface quite badly ...

> It means that it's next to impossible for a distro installer to support
> suspend-to-swapfile. 

Not necessarily.  After creating the swap file the installer can bmap it
and figure out the offset from there (it will require some rescaling, but the
code for that is in mm/swapfile.c).

> It's also incredibly fragile to rely on that file always remaining in that
> part of the disk. 

Well, if you don't delete it, it'll stay there. ;-)

The entire problem is we can't use file names during resume, because we can't
mount filesystems at that time, so we need to represent the swap header's
location in a filesystem-independent way.

Greetings,
Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/