> Now that we always keep the swap cache intact in mm/vmscan.c and only
> reclaim it in mm/filemap.c, we might in fact be safe omiting the swap
> lock. I'd be nervous about it without a _thorough_ audit of the code,
> though, as this particular race is hard to reproduce.
Plan: add a printk() for it and wait for someone to notice.
If you hear nothing by 2.2.3, get rid of the old crud.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/