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] [day] [month] [year] [list]
Message-ID: <45512E9C.9030702@goop.org>
Date:	Tue, 07 Nov 2006 17:10:52 -0800
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Rusty Russell <rusty@...tcorp.com.au>
CC:	Andrew Morton <akpm@...l.org>, Zachary Amsden <zach@...are.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Fix kunmap_atomic's use of kpte_clear_flush()

Rusty Russell wrote:
> On Tue, 2006-11-07 at 16:22 -0800, Jeremy Fitzhardinge wrote:
>   
>> kunmap_atomic() will call kpte_clear_flush with vaddr/ptep arguments
>> which don't correspond if the vaddr is just a normal lowmem address
>> (ie, not in the KMAP area).  This patch makes sure that the pte is
>> only cleared if kmap area was actually used for the mapping.
>>     
>
> Or in other words, if kmap_atomic() does nothing, kunmap_atomic() should
> do nothing.
>   

Sure.  I guess there's no particular reason why kmap_atomic() couldn't 
always map, but I guess avoid the pagetable updates is worthwhile.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ