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: <520547FB.5080706@infradead.org>
Date:	Fri, 09 Aug 2013 12:50:19 -0700
From:	Randy Dunlap <rdunlap@...radead.org>
To:	Jason Cooper <jason@...edaemon.net>
CC:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-pci <linux-pci@...r.kernel.org>
Subject: Re: linux-next: Tree for Aug 8 (not CONFIG_PCI_MSI conflict)

On 08/09/13 11:50, Jason Cooper wrote:
> Randy,
> 
> On Fri, Aug 09, 2013 at 09:41:38AM -0700, Randy Dunlap wrote:
>> On 08/09/13 07:59, Jason Cooper wrote:
>>> Randy,
>>>
>>> On Thu, Aug 08, 2013 at 01:03:04PM -0700, Randy Dunlap wrote:
>>>> On 08/08/13 00:08, Stephen Rothwell wrote:
>>>>> Hi all,
>>>>>
>>>>> Changes since 20130807:
>>>>>
>>>>
>>>> on i386 and x86_64:
>>>> when CONFIG_PCI_MSI is not enabled:
>>>>
>>>> There are many of these errors:
>>>> include/linux/msi.h:65:6: error: expected identifier or '(' before 'void'
>>>> include/linux/msi.h:65:6: error: expected ')' before numeric constant
>>>>
>>>> because arch/x86/include/asm/pci.h defines:
>>>> #define default_teardown_msi_irqs	NULL
>>>
>>> Do you have an example config you used?
>>
>> Sure, attached. (or I have 14 of them)
> 
> Thanks, I was able to reproduce the error.  I'm not real familiar with
> this area of the code, but the relief is it doesn't appear to be caused
> by the mvebu changes (well, relief for us ;-) ).
> 
> At any rate, give this a spin and see if it works for you
> 
> If it's acceptable, I'll do an official patch for Bjorn.

Works for me -- tested with PCI_MSI enabled & disabled.
Thanks.

Acked-by: Randy Dunlap <rdunlap@...radead.org>

> thx,
> 
> Jason.
> 
> ---------->8----------
> diff --git a/arch/x86/include/asm/pci.h b/arch/x86/include/asm/pci.h
> index d9e9e6c..6169414 100644
> --- a/arch/x86/include/asm/pci.h
> +++ b/arch/x86/include/asm/pci.h
> @@ -138,8 +138,8 @@ void default_restore_msi_irqs(struct pci_dev *dev, int irq);
>  #else
>  #define native_setup_msi_irqs		NULL
>  #define native_teardown_msi_irq		NULL
> -#define default_teardown_msi_irqs	NULL
> -#define default_restore_msi_irqs	NULL
> +void __weak default_teardown_msi_irqs(struct pci_dev *dev) { }
> +void __weak default_restore_msi_irqs(struct pci_dev *dev, int irq) { }
>  #endif
>  
>  #define PCI_DMA_BUS_IS_PHYS (dma_ops->is_phys)
> --


-- 
~Randy
--
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