Jeff Layton wrote:
Sure, I'm not disputing whether returning an error on open is right or wrong. The problem is that it's not expected. We've just unlinked the filename and returned success -- there is *no* reason that the create should fail here. An application programmer will (rightfully) consider this a bug.
I agree that failing the unlink if you can not do it is "the right thing to do"... but unless you have some magic to prevent anyone else from creating the file between that unlink and the create then in fact there is a reason the application can see the create fail after unlink succeeds :) -- 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
