linux-kernel - Re: pci_get_device_reverse(), why does Calgary need this?

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: <20080213181459.GA8960@kroah.com>
Date:	Wed, 13 Feb 2008 10:14:59 -0800
From:	Greg KH <greg@...ah.com>
To:	Muli Ben-Yehuda <muli@...ibm.com>
Cc:	jdmason@...zu.us, bzolnier@...il.com, linux-ide@...r.kernel.org,
	linux-pci@...ey.karlin.mff.cuni.cz, linux-kernel@...r.kernel.org,
	discuss@...-64.org
Subject: Re: pci_get_device_reverse(), why does Calgary need this?

On Wed, Feb 13, 2008 at 07:47:11PM +0200, Muli Ben-Yehuda wrote:
> On Wed, Feb 13, 2008 at 09:32:03AM -0800, Greg KH wrote:
> 
> > Is there some reason you aren't using the "real" PCI driver api here
> > and registering a pci driver for these devices?  That would take the
> > whole "loop over all pci devices" logic out of the code entirely.
> 
> I recall we had a reason, but I no longer recall what it was. Some
> reason the "real" PCI driver API didn't fit at the time. If someone
> were to whip up a working patch, I'd happily apply it.

"at the time"?  It's been in place since the 2.2 days :)

Is the problem that other drivers also want access to this PCI device
for some reason?

I'll whip up a patch for you to test with in a bit...

> > > Feel free to nuke it and walk the list forward.
> > 
> > So something like the patch below would be fine?
> 
> Yep, looks good. 
> 
> Acked-by: Muli Ben-Yehuda <muli@...ibm.com>

thanks for reviewing this.

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/