On Tue, Jan 21, 2014 at 05:31:39PM +0400, Pavel Shilovsky wrote: > It's not possible with the current API to do it through open syscall. > Another possibility is to look at /proc/locks. But I think we really > need O_DELETE flag that will force a file to be removed on close - we > will be able to do O_DENYDELETE checks atomically. I don't depend on this at open time. I can do it later with some syscall, that's fine. I just want to find a way to do it correctly. The problem is -- you can't "try" an unlink. So we have to probe whether we can unlink. And opening for O_DENYDELETE by no means says we *will* unlink. We just have to keep the option to do it exclusively. With best regards, Volker -- SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-370000-0, fax: +49-551-370000-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen http://www.sernet.de, mailto:kontakt@xxxxxxxxx -- 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
