Re: dev_mc_lock question.

From: kuznet@ms2.inr.ac.ru
Date: Tue Aug 22 2000 - 12:53:48 EST


Hello!

> They should lock dev->xmit_lock before accessing dev->mc_list now.

Of course. They have to acquire xmit_lock at least to serialize
itself wrt set_multicast_list in any case.

> The patch that replace dev_mc_lock is attached. The only problem that I
> see is that we execute dev_mc_read_proc() while holding dev->xmit_lock.
> Is this acceptable ?

I think this is acceptable. It is rarely used and it is pretty
silly to create new lock just to make it happy.

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



This archive was generated by hypermail 2b29 : Wed Aug 23 2000 - 21:00:07 EST