Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932086AbaAUORX (ORCPT ); Tue, 21 Jan 2014 09:17:23 -0500 Received: from mail.SerNet.de ([193.175.80.2]:59283 "EHLO mail.SerNet.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754472AbaAUORV (ORCPT ); Tue, 21 Jan 2014 09:17:21 -0500 Date: Tue, 21 Jan 2014 15:17:08 +0100 Date: Tue, 21 Jan 2014 15:17:08 +0100 From: Volker Lendecke To: Pavel Shilovsky Cc: Kernel Mailing List , linux-cifs , linux-fsdevel , Linux NFS Mailing list , wine-devel@winehq.org Subject: Re: [PATCH v7 0/7] Add O_DENY* support for VFS and CIFS/NFS Reply-To: Volker.Lendecke@SerNet.DE References: <1389953232-9428-1-git-send-email-piastry@etersoft.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Message-Id: Organization: SerNet GmbH, Goettingen, Germany Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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@sernet.de -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/