[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Killing JFFS under 2.2
David Woodhouse wrote:
> email@example.com said:
> > If I'm right, then I see two possible fixes - either stick a big
> > mutex around the (allocate,write) code, or have all node writes done
> > sequentially from a single kernel thread.
> There's a third possibility - make the jffs_scan_flash() code detect this
> and handle it appropriately. Not sure how, though.
If it has already found some data in the scan (the head), each free
space should be set as dirty. Then the GC should be able to repair the