Valerie Aurora: > I think what people will expect is that we copy up in that case. I > can think of ways this can go wrong, but perhaps that should be an > explicit requirement on the top-layer file system, that it can handle > create/unlink() in a directory without write permission. I am not sure such requirement is the right way. How about delegating open() to keventd or some other workqueue which will succeed to create files under a directory without write permission? Of course, we should handle some error cases after creating a file. J. R. Okajima -- 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
