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] [day] [month] [year] [list]
Message-ID: <20151116110622.GL8644@n2100.arm.linux.org.uk>
Date:	Mon, 16 Nov 2015 11:06:22 +0000
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	yamada.masahiro@...ionext.com
Cc:	arnd@...db.de, linux-arm-kernel@...ts.infradead.org,
	arm@...nel.org, mmarek@...e.com, olof@...om.net,
	linux-kbuild@...r.kernel.org, jamie@...ieiles.com,
	agross@...eaurora.org, kernel@...gutronix.de,
	gregory.clement@...e-electrons.com, linux-sh@...r.kernel.org,
	tsahee@...apurnalabs.com, linux-arm-msm@...r.kernel.org,
	linus.walleij@...aro.org, galak@...eaurora.org,
	plagnioj@...osoft.com, dinguyen@...nsource.altera.com,
	baohua@...nel.org, shiraz.linux.kernel@...il.com,
	rjui@...adcom.com, patrice.chotard@...com, kernel@...inux.com,
	soren.brinkmann@...inx.com, horms@...ge.net.au,
	michal.simek@...inx.com, heiko@...ech.de,
	linux-rockchip@...ts.infradead.org, linux-soc@...r.kernel.org,
	davidb@...eaurora.org, sbranden@...adcom.com, vireshk@...nel.org,
	alexandre.belloni@...e-electrons.com, kyungmin.park@...sung.com,
	mappyland78@...il.com, k.kozlowski@...sung.com,
	bcm-kernel-feedback-list@...adcom.com, f.fainelli@...il.com,
	gnurou@...il.com, matthias.bgg@...il.com, kgene@...nel.org,
	thierry.reding@...il.com, robh@...nel.org,
	linux-kernel@...r.kernel.org, spear-devel@...t.st.com,
	sebastian.hesselbarth@...il.com, sudeep.holla@....com,
	andrew@...n.ch, linux-samsung-soc@...r.kernel.org,
	linux-mediatek@...ts.infradead.org, linux-tegra@...r.kernel.org,
	maxime.coquelin@...com, srinivas.kandagatla@...il.com,
	shawnguo@...nel.org, liviu.dudau@....com, jun.nie@...aro.org,
	lorenzo.pieralisi@....com, nicolas.ferre@...el.com,
	jason@...edaemon.net, swarren@...dotorg.org, khalasa@...p.pl,
	xuwei5@...ilicon.com, magnus.damm@...il.com, wens@...e.org,
	maxime.ripard@...e-electrons.com
Subject: Re: [PATCH] ARM: use "depends on" for SoC configs instead of "if"
 after prompt

On Mon, Nov 16, 2015 at 10:32:51AM +0000, yamada.masahiro@...ionext.com wrote:
> Hi Arnd,
> 
>  
> > On Monday 16 November 2015 12:06:10 Masahiro Yamada wrote:
> > > Many ARM sub-architectures use prompts followed by "if" conditional,
> > > but it is wrong.
> > >
> > > Please notice the difference between
> > >
> > >     config ARCH_FOO
> > >             bool "Foo SoCs" if ARCH_MULTI_V7
> > >
> > > and
> > >
> > >     config ARCH_FOO
> > >             bool "Foo SoCs"
> > >             depends on ARCH_MULTI_V7
> > >
> > > These two are *not* equivalent!
> > >
> > > In the former statement, it is not ARCH_FOO, but its prompt that
> > > depends on ARCH_MULTI_V7.  So, it is completely valid that ARCH_FOO is
> > > selected by another, but ARCH_MULTI_V7 is still disabled. As it is not
> > > unmet dependency, Kconfig never warns.  This is probably not what you
> > > want.
> > 
> > Did you encounter a case where someone actually did a 'select' on one of
> > those symbols? I probably introduced a lot of them and did not expect that
> > to happen.
> 
> No, for ARM sub-architectures.
> But, yes for the ARM core part.
> 
> 
> For example, the following entry in arch/arm/Kconfig is suspicous.
> 
> config PCI
>         bool "PCI support" if MIGHT_HAVE_PCI
>         help
>           Find out whether you have a PCI motherboard. PCI is the name of a
>           bus system, i.e. the way the CPU talks to the other stuff inside
>           your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
>           VESA. If you have PCI, say Y, otherwise N.
> 
> 
> 
> 
> Try "make ARCH=arm footbridge_defconfig" and check the .config file.
> 
> It defines CONFIG_PCI=y, but not CONFIG_MIGHT_HAVE_PCI.
> I am not sure this is a sane .config or not.

It's correct.  "MIGHT_HAVE_PCI" is used by platforms which _might_ _have_
_PCI_, not by platforms which _do_ _have_ _PCI_.  Platforms which _do_
_have_ _PCI_ select PCI directly, and because "MIGHT_HAVE_PCI" is not
set, users are not offered an option that they can never disable.

-- 
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
--
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