linux-kernel - Re: linux-next: Tree for Aug 12 (include/linux/pci.h)

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: <55CBCF96.7060102@intel.com>
Date:	Wed, 12 Aug 2015 15:58:30 -0700
From:	Tadeusz Struk <tadeusz.struk@...el.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Randy Dunlap <rdunlap@...radead.org>
CC:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-pci <linux-pci@...r.kernel.org>,
	Herbert Xu <herbert@...dor.apana.org.au>,
	Michal Marek <mmarek@...e.cz>
Subject: Re: linux-next: Tree for Aug 12 (include/linux/pci.h)

Hi,
On 08/12/2015 02:53 PM, Stephen Rothwell wrote:
> On Wed, 12 Aug 2015 11:05:36 -0700 Randy Dunlap <rdunlap@...radead.org> wrote:
>> >
>> > on i386 or x86_64:
>> > 
>> > Many (repeated) errors like this one:
>> > 
>> > ../include/linux/pci.h:390:12: error: âstruct pci_devâ has no member named âphysfnâ
>> > 
>> > when CONFIG_PCI_ATS is not enabled.
> Maybe caused by commit
> 
>   dd0f368398ea ("crypto: qat - Add qat dh895xcc VF driver")
> 
> from the crypto tree Which adds a
> 
>   select PCI_IOV
> 
> to drivers/crypto/qat/Kconfig without the necessary
> 
>   select PCI
> 
> but PCI_IOV selects PCI_ATS, so I am not sure what happened here.  I am
> assuming that your config has PCI_IOV enabled?  What about PCI?

There is a patch submitted, but not yet applied
https://patchwork.kernel.org/patch/6994171/
maybe it will help?
--
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/