linux-kernel - Re: Pagecache zeroing: zero_user_segment, zero_user_segments and zero

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: <464AA285.4010309@yahoo.com.au>
Date:	Wed, 16 May 2007 16:19:49 +1000
From:	Nick Piggin <nickpiggin@...oo.com.au>
To:	Christoph Lameter <clameter@....com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	Satyam Sharma <satyam.sharma@...il.com>,
	Nate Diller <nate.diller@...il.com>
Subject: Re: Pagecache zeroing: zero_user_segment, zero_user_segments and
 zero_user

Christoph Lameter wrote:
> On Wed, 16 May 2007, Nick Piggin wrote:
> 
> 
>>Well sure, if that's all Christoph is worried about, then it isn't
>>really valid because in generic code we have to follow the architecture
>>abstraction API -- there is no "non highmem platform" in generic code :)
> 
> 
> But there is a default KM_USER0 that is used in many functions.
> 
> F.e.
> 
> filemap_copy_from_user *_iovec xip_truncate_page clear_user_highpage 
> clear_highpage copy_user_highpage copy_highpage
> 
> So explicitly mentioning KM_USER0 in every function call is not a 
> requirement.

You probably have an argument there... but that's not to do with
highmem platforms or not.

-- 
SUSE Labs, Novell Inc.
-
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/