[lkml]   [2000]   [Aug]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: dev_mc_lock question.

> 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.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:37    [W:0.066 / U:0.676 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site