On Tue, Jul 09, 2019 at 10:23:35AM +0800, Hillf Danton wrote: > > I don't think this is the correct fix. It's being called with kobj > > whose parent's sysfs node is dangling. It gotta be fixed from the > > caller side. > > > Make sense? > > --- a/lib/kobject.c > +++ b/lib/kobject.c
No, I meant that the problem likely is in the driver which is calling into the generic layer with a dead parent. We shouldn't be working around that from generic layer. Thanks. -- tejun
