Probs with port to 2.4.18

[David Woodhouse]

On Wed, 2003-12-03 at 14:23 -0500, Joan Dyer wrote:
> However what seems to be the underlying problem is a non-coordinated 
> write, while/during erase.   With my port, wbuf.c (which references the 
> erase_completion lock) is not used. 
> 
> Should I protect the write in writev.c with a call on the lock? 

No. You should not read, write or erase the flash with the
erase_completion_lock spinlock held. The underlying flash driver is
expected to deal with concurrent access for itself.

-- 
dwmw2