lkml.org 
[lkml]   [2003]   [Jun]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [PATCH][ATM] use rtnl_{lock,unlock} during device operations (take 2)
From
   From: chas williams <chas@cmf.nrl.navy.mil>
Date: Thu, 05 Jun 2003 11:28:47 -0400

thanks to someone for pointing out to me my flub when i errantly
converted a spin_unlock to rtnl_lock (it in a very rarely, never
in fact as far as i know, used section of the code. this following
should now be even more correct.

[ATM]: use rtnl_{lock,unlock} during device operations

Are you sure nothing needs to walk the list in interrupt or softint
context? That's why you can't normally protect all of it using the
RTNL semaphore, because walks occur in non-sleepable contexts.

Read the comment above dev_base in drivers/net/Space.c to see what
the intended locking model is.
-
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/

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