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: <1322711557-8279-1-git-send-email-paul.gortmaker@windriver.com>
Date:	Wed, 30 Nov 2011 22:52:37 -0500
From:	Paul Gortmaker <paul.gortmaker@...driver.com>
To:	nicolas.pitre@...aro.org, linux@....linux.org.uk
Cc:	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: [PATCH] arm: add default value for PHYS_OFFSET Kconfig setting

Commit 1b9f95f8ade9efc2bd49f0e7b9dc61a038ac3eef introduced the new
Kconfig for PHYS_OFFSET but it did not specify a default value.

This has the undesired side effect of breaking an implictly used
trick for updating defconfigs on the fly for routine buildtesting
across all arch and all platforms, i.e.

  cp /path/to/somedefconfig .config ; yes "" | make oldconfig

In particular, the at91x40_defconfig will enter an infinite loop
with the above, since there is no default value, and conf will just
keep asking for one, and "yes" will keep feeding in a line return.

Signed-off-by: Paul Gortmaker <paul.gortmaker@...driver.com>

diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 44789ef..90a475e 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -221,6 +221,7 @@ config NEED_MACH_MEMORY_H
 
 config PHYS_OFFSET
 	hex "Physical address of main memory"
+	default 0x00000000
 	depends on !ARM_PATCH_PHYS_VIRT && !NEED_MACH_MEMORY_H
 	help
 	  Please provide the physical address corresponding to the
-- 
1.7.7.2

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ