| 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
| ||
|
Date: Sun, 15 Dec 2013 08:21:36 +1100 From: Nigel Cunningham <nigel@...elcunningham.com.au> To: Tejun Heo <tj@...nel.org>, "Rafael J. Wysocki" <rafael.j.wysocki@...el.com> CC: Jens Axboe <axboe@...nel.dk>, tomaz.solc@...lix.org, aaron.lu@...el.com, linux-kernel@...r.kernel.org, Oleg Nesterov <oleg@...hat.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Fengguang Wu <fengguang.wu@...el.com> Subject: Re: [PATCH] libata, freezer: avoid block device removal while system is frozen Hi. On 15/12/13 07:36, Tejun Heo wrote: > On Sat, Dec 14, 2013 at 03:31:21PM -0500, Tejun Heo wrote: >> So, all this is about hibernation? Does that mean that it's safe to >> unfreeze before invoking resume? ie. we currently do, >> >> freeze >> suspend devs >> resume devs >> unfreeze >> >> If we can just do, >> >> freeze >> suspend devs >> unfreeze >> resume devs > Ummm... even better, does that mean, in the long term, we can decouple > freezing and device pm operations? If this is just about hibernation, > there's no reason to wrap device driver pm ops with freezer, right? > > Thanks. > Rafael has spent far more time than me thinking about the semantics here, so I'd like to defer to him. Rafael?... Regards, Nigel -- 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/
Powered by blists - more mailing lists