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:	Mon, 7 Jul 2014 01:52:33 +0100
From:	Grant Likely <>
To:	Linus Torvalds <>
Cc:	Rob Herring <>,
	Laura Abbott <>,
	"" <>,
	Linux Kernel Mailing List <>
Subject: Re: [GIT PULL] bug fix for devicetree memory parsing

On Sun, Jul 6, 2014 at 8:24 PM, Linus Torvalds
<> wrote:
> On Sun, Jul 6, 2014 at 2:37 AM, Grant Likely <> wrote:
>> Can you pull this bug fix into your tree please?
> I took it, but I think both your explanation and the patch itself is
> actually crap. It may fix the issue, but it's seriously confused.
> Your explanation says that it's a 32-bit platform issue. No it's not.
> Most 32-bit configurations still have a 64-bit phys_addr_t (ie
> PAE/LPAE etc).
> And the code is crap, because it uses ULONG_MAX etc in ways that
> simply make no f*cking sense. And why does it care about sizeof?
> Why does the code not just do something like
>   #define MAX_PHYS_ADDR ((phys_addr_t) ~0)
> and then do
>   if (base > MAX_PHYS_ADDR || base + size > MAX_PHYS_ADDR)
>     ...

Sure. I'll make sure a cleanup patch gets written and queued up.

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