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: <1340767488.17253.4.camel@cr0>
Date:	Wed, 27 Jun 2012 11:24:48 +0800
From:	Cong Wang <amwang@...hat.com>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	David Howells <dhowells@...hat.com>
Subject: Re: [PATCH 04/12] frv: remove km_type definitions

On Tue, 2012-06-26 at 22:25 +0200, Geert Uytterhoeven wrote:
> 
> "enum km_type" and "__KM_CACHE" are still used in
> arch/frv/include/asm/highmem.h:

Oops! I missed __KM_* types... Fortunately, the following patch could
probably fix it.

Thanks!

----------------------->

All callers of kmap_atomic_primary() use __KM_CACHE, so it can be
removed safely, and __kmap_atomic_primary() only check if 'type' if
__KM_CACHE or not, so 'type' can be changed to a boolean as well.

Ditto for kunmap_atomic_primary()/__kunmap_atomic_primary().


View attachment "frv.diff" of type "text/x-patch" (5752 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ