Hello! > Here is a patch which may not solve the underlying This does not. refcnt cannot be <1 at this point. > assuming that the latter messages aren't serious? They are fatal. Machine must be rebooted after them. > I hope the networking gurus can find the real bugs here. Well, someone forgets to grab refcnt or makes redundant dev_put. Try to catch this, f.e. adding BUG() to the places where fatal messages are generated to get backtraces. Alexey - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- [PATCH] to deal with bad dev->refcnt in unregi... Thomas Hood
- Re: [PATCH] to deal with bad dev->refcnt ... kuznet
- Re: [PATCH] to deal with bad dev->refcnt ... Thomas Hood
- Re: [PATCH] to deal with bad dev->refcnt ... Thomas Hood
- Re: [PATCH] to deal with bad dev->refcnt ... Thomas Hood
- Re: [PATCH] to deal with bad dev->refcnt ... Thomas Hood
- Re: [PATCH] to deal with bad dev->ref... Arnaldo Carvalho de Melo
- Re: [PATCH] to deal with bad dev->refcnt ... Thomas Hood
- [PATCH] fix bad dev->refcnt in unregi... Arnaldo Carvalho de Melo
- Re: [PATCH] to deal with bad dev->refcnt ... Thomas Hood
- Re: [PATCH] to deal with bad dev->refcnt ... Thomas Hood

