linux-kernel - Re: [PATCH] Fix corruption of CONFIG_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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 31 May 2011 09:53:06 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	Ted Ts'o <tytso@....edu>, x86@...nel.org,
	linux-kernel@...r.kernel.org,
	Alexey Dobriyan <adobriyan@...il.com>,
	Randy Dunlap <rdunlap@...otime.net>
Subject: Re: [PATCH] Fix corruption of CONFIG_X86_32 in 'make oldconfig'

* David Woodhouse <dwmw2@...radead.org> wrote:

> And then this legacy trick of using the obsolete $ARCH settings to 
> override the setting of CONFIG_64BIT can be deprecated.

Sigh, nope. The two legacies we have should simply be turned into 
trivial aliases that map to the newfangled CONFIG_*=y way of doing 
things.

I'll always prefer typing:

  make ARCH=x86_64 ...

To:

  make ARCH=x86 CONFIG_64BIT=y ...

And others have expressed that in this thread too.

Really, guys, please stop breaking existing tools!

There is no problem to solve here, having ARCH=i386 and ARCH=x86_64 
around does not hurt anyone, is well established and actively helps 
people so what's your problem?

I'll be happy to learn the new methods and will happily add them to 
the toolbox of existing methods.

Thanks,

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