linux-kernel - Re: [PATCH] Freeze bdevs when freezing processes.

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: <200610231620.56459.rjw@sisk.pl>
Date:	Mon, 23 Oct 2006 16:20:55 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Nick Piggin <nickpiggin@...oo.com.au>
Cc:	Nigel Cunningham <ncunningham@...uxmail.org>,
	Andrew Morton <akpm@...l.org>,
	LKML <linux-kernel@...r.kernel.org>, Pavel Machek <pavel@....cz>
Subject: Re: [PATCH] Freeze bdevs when freezing processes.

On Monday, 23 October 2006 16:15, Nick Piggin wrote:
> Rafael J. Wysocki wrote:
> 
> > This case is a bit special.  I don't think it would be right to require every
> > device driver writer to avoid modifying RCU pages from the interrupt
> > context, because that would break the suspend to disk ...
> > 
> > Besides, if there is an RCU page that we _know_ we can use to store the image
> > in it, we can just include this page in the image without copying.  This
> > already gives us one extra free page for the rest of the image and we can
> > _avoid_ creating two images which suspend2 does and which adds a _lot_ of
> > complexity to the code.
> 
> If you don't mind me asking... what are these RCU pages you speak of?
> I couldn't work it out by grepping kernel/power/*

Oops, s/RCU/LRU/g (shame, shame).

Sorry for the confusion.


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