linux-kernel - Re: CONFIG_HIGHPTE vs. sub-page page tables.

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]

Date:	Sun, 10 Feb 2008 10:41:08 +0100
From:	Martin Schwidefsky <schwidefsky@...ibm.com>
To:	Mike Frysinger <vapier.adi@...il.com>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: CONFIG_HIGHPTE vs. sub-page page tables.

On Sun, 2008-02-10 at 04:25 -0500, Mike Frysinger wrote:
> i guess my point was more: the pgtable_t typdef is new therefore it
> must be defined for every architecture.  your ability to directly
> cross-compile and/or test a subset is great, but posting a change that
> is know for a fact to break arches you didnt update seems like a bad
> idea.  even if you just included the obvious-but-not-compile-tested
> changes and included the linux-arch@...r alias instead would have been
> better than nothing
> -mike

The patch was posted multiple times on linux-arch and it has been part
of -mm for 3 months. Plenty of time for the arch maintainers to notice.
And without the pte_pfn_t change it would compile on a nommu
architecture even without the typedef. That is why I didn't add the new
typedef to the nommu archs. Which turned out to be a mistake after the
pte_pfn_t change has been added but the problem is fixed with the patch
sent yesterday, isn't?

-- 
blue skies,
  Martin.

"Reality continues to ruin my life." - Calvin.


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