linux-kernel - Re: [PATCH] Thaw userspace and kernel space separately.

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 25 Oct 2006 10:45:40 -0700 (PDT)
From:	dean gaudet <dean@...tic.org>
To:	Andrew Morton <akpm@...l.org>
cc:	Nigel Cunningham <ncunningham@...uxmail.org>, rjw@...k.pl,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Thaw userspace and kernel space separately.

On Mon, 23 Oct 2006, Andrew Morton wrote:

> > On Mon, 23 Oct 2006 22:00:11 +1000 Nigel Cunningham <ncunningham@...uxmail.org> wrote:
> > If you can only thaw the kernel threads, you can free memory without
> > restarting userspace or deadlocking against a frozen kjournald.
> > 
> 
> kjournald will not participate in writing to swapfiles.
> 
> The situation where we would need this feature is where the loop driver is
> involved in the path-to-disk.  But I doubt if that's a thing we'd want to
> support.

dm-crypt?  that seems like a very important thing to support for suspend 
to disk.

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