linux-kernel - Re: [RFC][PATCH] kmap_atomic

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: <20091008155344.GA11727@elte.hu>
Date:	Thu, 8 Oct 2009 17:53:44 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Peter Zijlstra <peterz@...radead.org>, Avi Kivity <avi@...hat.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"hugh.dickins" <hugh.dickins@...cali.co.uk>,
	David Howells <dhowells@...hat.com>,
	lkml <linux-kernel@...r.kernel.org>,
	linux-arch <linux-arch@...r.kernel.org>
Subject: Re: [RFC][PATCH] kmap_atomic_push


* Peter Zijlstra <peterz@...radead.org> wrote:

> The below patchlet changes the kmap_atomic interface to a stack based 
> one that doesn't require the KM_types anymore.
> 
> This significantly simplifies some code (more still than are present 
> in this patch -- ie. pte_map_nested can go now)
> 
> This obviously requires that push and pop are matched, I fixed a few 
> cases that were not properly nested, the (x86) code checks for this 
> and will go BUG when trying to pop a vaddr that isn't the top one so 
> abusers should be rather visible.

Looks great IMO! Last i proposed this i think either Andrew or Avi had 
second thoughts about the hard-to-calculate worst-case mapping limit - 
but i dont think that's a big issue.

Lets not change the API names though - the rule is that map/unmap must 
be properly nested.

	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/