linux-kernel - Re: irq allocation for pci drivers

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

Message-ID: <20110413034043.GA813@suse.de>
Date:	Tue, 12 Apr 2011 20:40:43 -0700
From:	Greg KH <gregkh@...e.de>
To:	KY Srinivasan <kys@...rosoft.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
	"virtualization@...ts.osdl.org" <virtualization@...ts.osdl.org>
Subject: Re: irq allocation for pci drivers

On Tue, Apr 12, 2011 at 11:57:22PM +0000, KY Srinivasan wrote:
> Greg,
> 
>  
> 
> Has something changed in the PCI code in the Linux-next tree – 2.6.39-rc1-12
> with
> 
> regards to irq allocation? Earlier (a few weeks ago), the vmbus driver would
> get the irq allocated as part
> 
> of it being now a pci driver. Currently, however the system is setting pdev->
> irq to
> 
> 0 and needless to say, request_irq() is failing.

{sigh}  Please fix your email client...

Anyway, I have no idea, please use 'git bisect' to track down the
problem commit that causes this.

thanks,

greg k-h
--
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/