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]
Message-ID: <20160713202611.GA32111@amd>
Date:	Wed, 13 Jul 2016 22:26:11 +0200
From:	Pavel Machek <pavel@....cz>
To:	"Rafael J. Wysocki" <rafael@...nel.org>
Cc:	Chen Yu <yu.c.chen@...el.com>, Linux PM <linux-pm@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	Len Brown <len.brown@...el.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] PM / hibernate: Introduce snapshot test mode for
 hibernation

On Wed 2016-07-13 22:04:27, Rafael J. Wysocki wrote:
> On Wed, Jul 13, 2016 at 7:01 PM, Pavel Machek <pavel@....cz> wrote:
> > Hi!
> >
> >> >>and then swapon the swap device, and do a testing. This should be safer?
> >> >Yeah, that's the way. Read-only root is other option.
> >> >
> >> >>>I guess updating documentation would be welcome from my side,
> >> >>>otherwise it should be ok.
> >> >>OK, I'll  update the documents.
> >> >Just add fat warning into the documentation.
> >> OK.
> >
> > Actually... If you could add
> >
> > printk(KERN_ALERT "Hibernation image written. If you have any
> > filesystems mounted read-write and attempt to resume, you'll corrupt
> > your data. To prevent that, remove the hibernation image.\n")
> >
> > ...I guess that would save someone's filesystem. (Yes, very high
> > loglevel. If you attempt to do this from anything else then singleuser
> > or initrd, you are asking for problems, so... lets make sure user sees
> > it.)
> 
> Please see the new version of this patch:
> https://patchwork.kernel.org/patch/9226837/

New version changes nothing, right? You still need to be sure
filesystems are not mounted r/w. So I would still like to see printk()
with warning.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ