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  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:	Thu, 7 Aug 2014 10:22:28 -0500
From:	Rob Herring <>
To:	Max Filippov <>
Cc:	Kees Cook <>,
	LKML <>,
	Mark Salter <>, Liu hua <>,
	Rabin Vincent <>,
	Nikolay Borisov <>,
	Nicolas Pitre <>,
	Leif Lindholm <>,
	Tomasz Figa <>,
	Doug Anderson <>,
	Will Deacon <>,
	Laura Abbott <>,
	Catalin Marinas <>,
	Russell King - ARM Linux <>,
Subject: Re: [PATCH 1/7] arm: use generic fixmap.h

On Thu, Aug 7, 2014 at 10:15 AM, Max Filippov <> wrote:
> Hi,
> On Wed, Aug 6, 2014 at 11:32 PM, Kees Cook <> wrote:
>> ARM is different from other architectures in that fixmap pages are indexed
>> with a positive offset from FIXADDR_START.  Other architectures index with
>> a negative offset from FIXADDR_TOP.  In order to use the generic fixmap.h
> Does anybody know if there's any reason why generic fixmap.h uses negative
> offsets? It complicates things with no obvious benefit if you e.g. try to align
> virtual address in the fixmap region with physical page color (that's why I've
> switched xtensa to positive fixmap addressing in v3.17).

No, but each arch doing it differently is even more annoying.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists