linux-kernel - Re: [RFC v6][PATCH 0/9] Kernel based checkpoint/restart

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:	Fri, 10 Oct 2008 17:39:51 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Dave Hansen <dave@...ux.vnet.ibm.com>
Cc:	Oren Laadan <orenl@...columbia.edu>, jeremy@...p.org,
	arnd@...db.de, containers@...ts.linux-foundation.org,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	Alexander Viro <viro@...iv.linux.org.uk>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [RFC v6][PATCH 0/9] Kernel based checkpoint/restart


* Dave Hansen <dave@...ux.vnet.ibm.com> wrote:

> On Thu, 2008-10-09 at 15:44 +0200, Ingo Molnar wrote:
> > there might be races as well, especially with proxy state - and 
> > current->flags updates are not serialized.
> > 
> > So maybe it should be a completely separate flag after all? Stick it 
> > into the end of task_struct perhaps.
> 
> What do you mean by proxy state?  nsproxy?

it's a concept: one task installing some state into another task (which 
state must be restored after a checkpoint event), while that other task 
is running. Such as a pi-futex state for example.

So a task can acquire state not just by its own doing, but via some 
other task too.

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