linux-kernel - Re: [RFC 1/7] cpuset write dirty map

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]

Message-ID: <Pine.LNX.4.64.0706041138410.24412@schroedinger.engr.sgi.com>
Date:	Mon, 4 Jun 2007 11:39:40 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Ethan Solomita <solo@...gle.com>
cc:	linux-mm@...ck.org, LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...gle.com>, a.p.zijlstra@...llo.nl
Subject: Re: [RFC 1/7] cpuset write dirty map

On Thu, 31 May 2007, Ethan Solomita wrote:

> The dirty map is only cleared (or freed) when the inode is cleared.
> At that point no pages are attached to the inode anymore and therefore it can
> be done without any locking. The dirty map therefore records all nodes that
> have been used for dirty pages by that inode until the inode is no longer
> used.
> 
> Originally by Christoph Lameter <clameter@....com>

You should preserve my Signed-off-by: since I wrote most of this. Is there 
a changelog?

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