On Tue, 5 Dec 2006, Maciej W. Rozycki wrote:
>
> One way of avoiding it is calling flush_scheduled_work() from
> phy_stop_interrupts(). This is fine as long as a caller of
> phy_stop_interrupts() (not necessarily the immediate one calling into
> libphy) does not hold the netlink lock.
>
> If a caller indeed holds the netlink lock, then a driver effectively
> calling phy_stop_interrupts() may arrange for the function to be itself
> scheduled through the event queue. This has the effect of avoiding the
> race as well, as the queue is processed in order, except it causes more
> hassle for the driver.
I would personally be ok with "flush_scheduled_work()" _itself_ noticing
that it is actually waiting to flush "itself", and just being a no-op in
that case.
However, having outside code do that detection for it seems to be ugly as
hell. And something like the network drievr layer shouldn't know about
keventd details like this.
So if you can move that deadlock avoidance logic into
"flush_scheduled_work()" itself, we'd avoid the stupid export, and we'd
also avoid the driver layer having to care about these things. It would
still be _ugly_, but I think it would be less so.
Hmm?
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
