linux-kernel - Re: ARCH_FREE_PTE_NR 5350 on x86

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]

Date:	Tue, 23 Oct 2007 06:29:18 +1000
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Hugh Dickins <hugh@...itas.com>
Cc:	Nick Piggin <nickpiggin@...oo.com.au>,
	Alok kataria <alokkataria1@...il.com>, Andi Kleen <ak@...e.de>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org
Subject: Re: ARCH_FREE_PTE_NR 5350 on x86_64

> Agreed.  No hurry, but thanks to Alok for reminding us.
> CC'ing Ben since he's the one most active in mmu_gathering these days.
> CC'ing Thomas lest he's puzzling over it in the x86 merge.

Hrm... yes, that stuff sucks. I've had my work on mmu gather on hold
since KS due to other priorities showing up, but I'll get back to it
soon and put that on the todo list.

The main pain here is the immap_lock. I have various plans to get rid of
preemption blocking in the main mmu gather (the stuff we discussed
already basically), but the immap_lock must stay, so we need to keep
something akin to immap_lock.

With the new approach, the disconnect between ZAP_BLOCK_SIZE and
whatever we use to represent the size of a batch might still be relevant
for the cases where we aren't holding that lock.

I'll get back to that stuff soon and we can then discuss the details.

Ben.

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