linux-kernel - Re: linux-next: Tree for July 12 (pci)

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: <CAL-B5D2D8WfDgrQoz4AVojXxavrhap2XPRyhkR3AeD4NNZHHxQ@mail.gmail.com>
Date:	Fri, 13 Jul 2012 14:42:45 -0600
From:	Myron Stowe <myron.stowe@...il.com>
To:	Randy Dunlap <rdunlap@...otime.net>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	linux-pci <linux-pci@...r.kernel.org>
Subject: Re: linux-next: Tree for July 12 (pci)

On Thu, Jul 12, 2012 at 10:11 AM, Randy Dunlap <rdunlap@...otime.net> wrote:
> On 07/11/2012 11:03 PM, Stephen Rothwell wrote:
>
>> Hi all,
>>
>> Changes since 20120710:
>>
>>
>> The pci tree lost its conflicts.
>
>
> on x86_64:
>
> drivers/built-in.o: In function `pci_bus_add_device':
> (.text+0x4f62): undefined reference to `pci_fixup_final_inited'
>
>
> when CONFIG_PCI_QUIRKS is not enabled.
>
I just posted a patch to  resolve what you encountered.  Would you mind giving
it a try and reporting back with the results?

It's obvious what you ran into, with CONFIG_PCI_QUIRKS not enabled,
./drivers/pci/quirks.o ends up not being generated and included in the
kernel thus
the unresolved reference from ./drivers/pci/bus.o.

I tried to reproduce the failure by disabling my .config file's
CONFIG_PCI_QUIRKS
entry (which in turn required me to enable CONFIG_EXPERT) but that was not
enough to encounter the unresolved reference - although it *should* have been.

Myron
>
> --
> ~Randy
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
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/