linux-kernel - [PATCH] kconfig: don't select 64 bit option on sparc32 all{yes,mod}config

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-next>] [day] [month] [year] [list]

Message-Id: <1287762484-8154-1-git-send-email-namhyung@gmail.com>
Date:	Sat, 23 Oct 2010 00:48:04 +0900
From:	Namhyung Kim <namhyung@...il.com>
To:	Roman Zippel <zippel@...ux-m68k.org>
Cc:	linux-kbuild@...r.kernel.org,
	"David S. Miller" <davem@...emloft.net>,
	linux-kernel@...r.kernel.org
Subject: [PATCH] kconfig: don't select 64 bit option on sparc32 all{yes,mod}config

The SPARC architecture provides 64BIT config option to select
build type and it is set to 1 on ARCH=sparc64 as a default value.
But in case of 32-bit, it is also set to 1 by the allyesconfig
logic, end result would be the same as of sparc64. So I think
it would be better if plain ARCH=sparc all{yes,mod}config do not
set it then we can test 32-bit build by default.

Signed-off-by: Namhyung Kim <namhyung@...il.com>
---
 scripts/kconfig/confdata.c |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)

diff --git a/scripts/kconfig/confdata.c b/scripts/kconfig/confdata.c
index 515253f..9820c77 100644
--- a/scripts/kconfig/confdata.c
+++ b/scripts/kconfig/confdata.c
@@ -1018,6 +1018,10 @@ void conf_set_all_new_symbols(enum conf_def_mode mode)
 			break;
 		}
 
+		/* Do not set 64 bit option when sparc32 allyesconfig */
+		if (sym->name && strcmp(sym->name, "64BIT") == 0 &&
+		    strcmp(getenv("ARCH"), "sparc") == 0)
+			sym->def[S_DEF_USER].tri = no;
 	}
 
 	sym_clear_all_valid();
-- 
1.7.0.4

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