linux-kernel - Re: [PATCH] libata, freezer: avoid block device removal while system is frozen

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: <20131214203652.GC4020@htj.dyndns.org>
Date:	Sat, 14 Dec 2013 15:36:52 -0500
From:	Tejun Heo <tj@...nel.org>
To:	Nigel Cunningham <nigel@...elcunningham.com.au>
Cc:	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
	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

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.

-- 
tejun
--
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/