On Mon, Mar 10, 2014 at 6:36 AM, Jeff Layton <jlayton@xxxxxxxxxx> wrote: > Allow locks_mandatory_area() to handle file-private locks correctly. > If there is a file-private lock set on an open file and we're doing I/O > via the same, then that should not cause anything to block. > > Handle this by first doing a non-blocking FL_ACCESS check for a > file-private lock, and then fall back to checking for a classic POSIX > lock (and possibly blocking). This is ugly, but it doesn't seem much worse than the existing code. :) --Andy -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
