linux-kernel - Re: [PATCH] Only show RESOURCES_64BIT on relevant architectures

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20071029151158.GC23138@fattire.cabal.ca>
Date:	Mon, 29 Oct 2007 11:11:58 -0400
From:	Kyle McMartin <kyle@...artin.ca>
To:	David Miller <davem@...emloft.net>
Cc:	linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Only show RESOURCES_64BIT on relevant architectures

On Sun, Oct 28, 2007 at 06:09:49PM -0700, David Miller wrote:
> From: Kyle McMartin <kyle@...artin.ca>
> Date: Sun, 28 Oct 2007 16:15:49 -0400
> 
> > To quote lolcats: CONFIG_RESOURCES_64BIT DO NOT WANT!
> > 
> > I *think* I have the logic of this right... Anyway, I was annoyed by
> > having to do the bloody ugly casts to unsigned long long in
> > arch-specific code. As near as I can tell, we only want this selectable
> > in the case of PAE on x86, and some random PPC and MIPS embedded boards.
> > 
> > For everyone else, it should be whatever the value of 64BIT is.
> > 
> > And I can be happy and continue using unsigned long and going about my
> > merry business.
> > 
> > Signed-off-by: Kyle McMartin <kyle@...artin.ca>
> 
> 32-bit sparc has 36-bit physical addresses and thus needs
> 64-bit resources too

I didn't realize this, since it wasn't set in any of the configs, or
select-ed by any of the Kconfig. Will add this in the next go 'round.

Cheers,
	Kyle
-
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/