From: Volker Lendecke <Volker.Lendecke@SerNet.DE>
To: Pavel Shilovsky <piastry@etersoft.ru>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-cifs <linux-cifs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux NFS Mailing list <linux-nfs@vger.kernel.org>,
wine-devel@winehq.org
Subject: Re: [PATCH v7 0/7] Add O_DENY* support for VFS and CIFS/NFS
Date: Tue, 21 Jan 2014 15:17:08 +0100
Date: Tue, 21 Jan 2014 15:17:08 +0100 [thread overview]
Message-ID: <E1W5c8k-0036ba-7A@intern.SerNet.DE> (raw)
In-Reply-To: <CAKywueQng9=u1YYwkYGCunWW8RBhARhJjEhBcoA6CKF6TrKSBg@mail.gmail.com>
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
next prev parent reply other threads:[~2014-01-21 14:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 10:07 [PATCH v7 0/7] Add O_DENY* support for VFS and CIFS/NFS Pavel Shilovsky
2014-01-17 10:07 ` [PATCH v7 1/7] VFS: Introduce new O_DENY* open flags Pavel Shilovsky
2014-01-17 18:18 ` One Thousand Gnomes
2014-01-20 10:45 ` Pavel Shilovsky
2014-01-20 13:34 ` One Thousand Gnomes
2014-01-21 13:19 ` Pavel Shilovsky
2014-02-01 13:57 ` Jeff Layton
2014-02-01 13:20 ` Jeff Layton
2014-02-04 12:03 ` Pavel Shilovsky
2014-02-04 12:21 ` Jeff Layton
2014-01-17 10:07 ` [PATCH v7 2/7] VFS: Add O_DENYDELETE support for VFS Pavel Shilovsky
2014-01-17 10:07 ` [PATCH v7 3/7] locks: Disable LOCK_MAND support for MS_SHARELOCK mounts Pavel Shilovsky
2014-01-17 10:07 ` [PATCH v7 4/7] CIFS: Add O_DENY* open flags support Pavel Shilovsky
2014-01-17 10:07 ` [PATCH v7 5/7] NFSD: Pass share reservations flags to VFS Pavel Shilovsky
2014-01-17 10:07 ` [PATCH v7 6/7] NFSv4: Add deny state handling for nfs4_state struct Pavel Shilovsky
2014-01-17 10:07 ` [PATCH v7 7/7] NFSv4: Add O_DENY* open flags support Pavel Shilovsky
2014-01-17 18:43 ` [PATCH v7 0/7] Add O_DENY* support for VFS and CIFS/NFS Frank Filz
2014-01-20 9:56 ` Pavel Shilovsky
2014-01-27 19:49 ` Frank Filz
2014-01-20 8:14 ` Volker Lendecke
2014-01-20 10:20 ` Pavel Shilovsky
2014-01-20 10:31 ` Volker Lendecke
2014-01-21 13:31 ` Pavel Shilovsky
2014-01-21 14:17 ` Volker Lendecke [this message]
2014-01-31 15:51 ` Pavel Shilovsky
-- strict thread matches above, loose matches on Subject: below --
2013-07-01 16:49 Pavel Shilovsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1W5c8k-0036ba-7A@intern.SerNet.DE \
--to=volker.lendecke@sernet.de \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=piastry@etersoft.ru \
--cc=wine-devel@winehq.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).