Re: BUG in i2c_detach_client

["Jean Delvare" <khali@linux-fr.org>]

Hi Andrew,

> > Will do. But I don't think that's it. I've been adding printks to
> > determine the execution path and it goes through the ERROR3 path in
> > asb100_detect(), which means AFACT that the error path in
> > asb100_detect_subclients() isn't taken:
> >
> >  ERROR3:
> >          i2c_detach_client(data->lm75[0]);
> >          kfree(data->lm75[1]);
> >          kfree(data->lm75[0]);
> >  ERROR2:
> >          i2c_detach_client(new_client); // <--- BUG() in here.
> >  ERROR1:
> >          kfree(data);
> >  ERROR0:
> >          return err;
>
> hm, the tree I have here doesn't do that.  What kernel do you have there?

I suspect that the bug will only show when the i2c-core and asb100
drivers (and the relevant i2c bus driver) are built into the kernel.
(See my previous post.)

Thanks,
--
Jean Delvare
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/