Re: linux-2.6.17-mm6: strange kobject message

From: Arjan van de Ven
Date: Fri Jul 07 2006 - 05:27:34 EST


On Fri, 2006-07-07 at 02:24 -0700, Andrew Morton wrote:

> hm.
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.17/2.6.17-mm6/broken-out/lockdep-annotate-8390c-disable_irq.patch
> didn't work.

-mm6 only had part 1; you also have part 2 now which should fix this one

> We've seen this reported a couple of times before. It could be a race in
> the tty layer where a newly-added vc has the same index as a going-away
> one which still has its sysfs file. Or it could be something else :(

that'd be a bug in the tty layer; the VC shouldn't be allowed to go away
until the sysfs file is gone (basic sysfs refcounting rules), and any
person keeping such a file open can delay that.
Now I can believe the tty layer having, ehm, suboptimal
refcounting/locking; I believe Alan is still trying to get it sane....

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