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  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]
Date:	Sat, 5 Apr 2008 08:53:23 -0700
From:	Greg KH <>
To:	Pierre Ossman <>
Cc:	LKML <>
Subject: Re: pci: add to global list before sysfs?

On Sat, Apr 05, 2008 at 11:57:27AM +0200, Pierre Ossman wrote:
> On Fri, 4 Apr 2008 14:01:32 -0700
> Greg KH <> wrote:
> > 
> > What "global list"?  You mean the one that I just deleted with my
> > patchset that is in -mm and going to be in 2.6.26?  :)
> > 
> *gnn*

Well the "global list" was not being used for anything, and it was being
created at the same time the driver core list was, so unless you wanted
to change the way that all pci devices were probed/created, it would not
have worked out.

> > How will changing the addition of the device to the list affect this
> > behavior?  Do you want to walk the list in your driver's probe function,
> > looking for the "subfunction" that is not yet added to the list?
> > 
> Yes. Things work fine when the driver is loaded after the entire PCI
> bus has been scanned, but not when new cards are hotplugged with the
> driver already present. I'd like the behaviour to be the same in both
> cases.

Why not just create a thread in your driver, or timer, and sleep until
you see the other devices?  If after a certian time you never do, then
bail out.

That should work properly for you for both cases (startup and loading


greg k-h
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists