> But running flush_scheduled_work() from within dev_close() is a very > sensible thing to do, and dev_close is called under rtnl_lock(). I can't argue with that -- this has actually bitten me in the past. Hmm, I'll try to understand why we need rtnl_lock() to cover dev_close... - R. - 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/
- References:
- [PATCH] Export current_is_keventd() for libphy
- From: Ben Collins <ben.collins@ubuntu.com>
- Re: [PATCH] Export current_is_keventd() for libphy
- From: Andrew Morton <akpm@osdl.org>
- Re: [PATCH] Export current_is_keventd() for libphy
- From: "Maciej W. Rozycki" <macro@linux-mips.org>
- Re: [PATCH] Export current_is_keventd() for libphy
- From: Andrew Morton <akpm@osdl.org>
- Re: [PATCH] Export current_is_keventd() for libphy
- From: Andy Fleming <afleming@freescale.com>
- Re: [PATCH] Export current_is_keventd() for libphy
- From: Andrew Morton <akpm@osdl.org>
- Re: [PATCH] Export current_is_keventd() for libphy
- From: Roland Dreier <rdreier@cisco.com>
- Re: [PATCH] Export current_is_keventd() for libphy
- From: Andrew Morton <akpm@osdl.org>
- [PATCH] Export current_is_keventd() for libphy
- Prev by Date: xtables/iptables and atkbd.c Spurious ACK on isa0060/serio0
- Next by Date: SAK and screen readers
- Previous by thread: Re: [PATCH] Export current_is_keventd() for libphy
- Next by thread: Re: [PATCH] Export current_is_keventd() for libphy
- Index(es):
 |