* device_find broken in 2.6.11?
@ 2005-07-08 4:16 Rusty Russell
2005-07-08 4:29 ` Greg KH
0 siblings, 1 reply; 4+ messages in thread
From: Rusty Russell @ 2005-07-08 4:16 UTC (permalink / raw)
To: Greg KH; +Cc: lkml - Kernel Mailing List
Hi Greg,
I was getting oopses in kset_find_obj when calling device_find in
2.6.11.12. Noone else in the kernel uses device_find, but I couldnt'
see anything wrong with it (mind you, I can't understand the
kset_find_obj code to judge it).
Iterating manually using bus_for_each_dev works though.
Known problem?
Rusty.
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: device_find broken in 2.6.11?
2005-07-08 4:16 device_find broken in 2.6.11? Rusty Russell
@ 2005-07-08 4:29 ` Greg KH
2005-07-08 15:36 ` Rusty Russell
0 siblings, 1 reply; 4+ messages in thread
From: Greg KH @ 2005-07-08 4:29 UTC (permalink / raw)
To: Rusty Russell; +Cc: lkml - Kernel Mailing List
On Fri, Jul 08, 2005 at 02:16:53PM +1000, Rusty Russell wrote:
> Hi Greg,
>
> I was getting oopses in kset_find_obj when calling device_find in
> 2.6.11.12. Noone else in the kernel uses device_find, but I couldnt'
> see anything wrong with it (mind you, I can't understand the
> kset_find_obj code to judge it).
>
> Iterating manually using bus_for_each_dev works though.
>
> Known problem?
Yup, there's a reason no one uses it. Use the version in 2.6.13-rc2, it
actually works.
What are you wanting to use it for?
thanks,
greg k-h
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: device_find broken in 2.6.11?
2005-07-08 4:29 ` Greg KH
@ 2005-07-08 15:36 ` Rusty Russell
2005-07-08 16:48 ` Greg KH
0 siblings, 1 reply; 4+ messages in thread
From: Rusty Russell @ 2005-07-08 15:36 UTC (permalink / raw)
To: Greg KH; +Cc: lkml - Kernel Mailing List
On Thu, 2005-07-07 at 21:29 -0700, Greg KH wrote:
> On Fri, Jul 08, 2005 at 02:16:53PM +1000, Rusty Russell wrote:
> >
> > I was getting oopses in kset_find_obj when calling device_find in
> > 2.6.11.12.
>
> Yup, there's a reason no one uses it. Use the version in 2.6.13-rc2, it
> actually works.
>
> What are you wanting to use it for?
The xenbus code wants to find if a device is new: the Xen code is
currently against on 2.6.11.12.
Thanks!
Rusty.
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: device_find broken in 2.6.11?
2005-07-08 15:36 ` Rusty Russell
@ 2005-07-08 16:48 ` Greg KH
0 siblings, 0 replies; 4+ messages in thread
From: Greg KH @ 2005-07-08 16:48 UTC (permalink / raw)
To: Rusty Russell; +Cc: lkml - Kernel Mailing List
On Sat, Jul 09, 2005 at 01:36:04AM +1000, Rusty Russell wrote:
> On Thu, 2005-07-07 at 21:29 -0700, Greg KH wrote:
> > On Fri, Jul 08, 2005 at 02:16:53PM +1000, Rusty Russell wrote:
> > >
> > > I was getting oopses in kset_find_obj when calling device_find in
> > > 2.6.11.12.
> >
> > Yup, there's a reason no one uses it. Use the version in 2.6.13-rc2, it
> > actually works.
> >
> > What are you wanting to use it for?
>
> The xenbus code
What is that? Any pointers to it?
> wants to find if a device is new:
new to whom? Busses usually drive the finding of new devices, so they
always know when a device has been found or goes away.
> the Xen code is currently against on 2.6.11.12.
If you have code that is using the driver core, it will need big changes
for 2.6.13 due to the internal rework that we have done. I suggest you
start now :)
Good luck,
greg k-h
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2005-07-08 16:49 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-07-08 4:16 device_find broken in 2.6.11? Rusty Russell
2005-07-08 4:29 ` Greg KH
2005-07-08 15:36 ` Rusty Russell
2005-07-08 16:48 ` Greg KH
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox