linux-kernel - staging: fsl-mc-bus: using MSI?

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>] [day] [month] [year] [list]

Date:   Wed, 18 Oct 2017 12:31:09 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     german.rivera@...escale.com,
        "devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Arnd Bergmann <arnd@...db.de>
Subject: staging: fsl-mc-bus: using MSI?

Hi,

I have seen a few randconfig builds where FSL_MC_BUS is enabled.
This selects GENERIC_MSI_IRQ_DOMAIN -- even if CONFIG_PCI and
CONFIG_PCI_MSI are not enabled.  (This is with COMPILE_TEST enabled.)

I see in the README.txt file that the DPAA2/MC does use some kind of
message interrupts.

Several of the source files #include <linux/msi.h>.
I guess that these files get whatever they need from <linux/msi.h>
even though several of the CONFIG_ options are not enabled.

Anyway, having GENERIC_MSI_IRQ_DOMAIN enabled without CONFIG_PCI and
CONFIG_PCI_MSI causes a couple of build errors -- with COMPILE_TEST.

../kernel/irq/msi.c: In function 'msi_domain_alloc_irqs':
../kernel/irq/msi.c:356:19: error: storage size of 'arg' isn't known
  msi_alloc_info_t arg;
                   ^

../drivers/base/platform-msi.c:37:19: error: field 'arg' has incomplete type
  msi_alloc_info_t arg;
                   ^

thanks,
-- 
~Randy