linux-kernel - Re: linux-next: Tree for May 6 (acpi: PCI=n)

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]

Message-Id: <20100506134211.e08c795a.randy.dunlap@oracle.com>
Date:	Thu, 6 May 2010 13:42:11 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Len Brown <lenb@...nel.org>, James Morris <jmorris@...ei.org>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-acpi@...r.kernel.org, linux-next@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for May 6 (acpi: PCI=n)

On Thu, 06 May 2010 16:29:42 -0400 (EDT) Len Brown wrote:

> > When CONFIG_PCI is not enabled:
> > 
> > arch/x86/kernel/acpi/boot.c:1034: error: 'pci_bus_type' undeclared
> > 
> > drivers/acpi/reboot.c:30: error:implicit declaration of function 'pci_find_bus'
> > drivers/acpi/reboot.c:30: warning: assignment makes pointer from integer without a cast
> > drivers/acpi/reboot.c:38: error:implicit declaration of function 'pci_bus_write_config_byte'
> 
> CONFIG_ACPI depends on CONFIG_PCI, so this file should not be build with 
> CONFIG_PCI=n.
> 
> Please let me know how you were able to generate this illegal 
> configuration.


Same TPM kconfig that selects ACPI without any other qualifications.

In 50 randconfig builds, 12 build failures were due to that one bad kconfig.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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/