linux-kernel - Re: [PATCH] Bugfix for VMI paravirt ops

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: <46158FBE.3090105@vmware.com>
Date:	Thu, 05 Apr 2007 17:09:34 -0700
From:	Zachary Amsden <zach@...are.com>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
CC:	Andi Kleen <ak@...e.de>, Andrew Morton <akpm@...l.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...l.org>
Subject: Re: [PATCH] Bugfix for VMI paravirt ops

Jeremy Fitzhardinge wrote:
> Zachary Amsden wrote:
>   
>> Well at this point, the "proper" fix is dependent on Jeremy's
>> kmap_atomic_pte changes, which are definitely too late to pull into
>> 2.6.21.  Can we just apply this patch please? 
>>     
>
> Hm, I think they're independent aren't they?  Your fix is about making
> lazy_mmu disable interrupts; that's independent of how highpte pages get
> mapped.

No, they are totally dependent.  The reason interrupts are disabled is 
to stop kmap_atomic in interrupt handlers.  With the kmap_atomic_pte 
changes, the whole interrupt disable jibberish goes away.

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