From: "Steve French" <smfrench@gmail.com>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"linux-cifs-client@lists.samba.org"
<linux-cifs-client@lists.samba.org>
Subject: Support for applications which need NFS or CIFS "share_deny" flags on open
Date: Tue, 2 Dec 2008 10:31:20 -0600 [thread overview]
Message-ID: <524f69650812020831q4e089b87k9a8306ac37f4234a@mail.gmail.com> (raw)
Some of the Wine community posted last month to the cifs mailing list
asking about a change needed for Wine for working properly over
network mounts, but the change is not really cifs specific and would
help other file systems as well so I wanted to mention it here. The
original post was:
http://marc.info/?l=linux-cifs-client&m=122505569315992&w=2
Support for the flags they suggest would be easy for cifs (the
protocol has a field for this, and cifs clients on various other OS
set it), and should be fairly easy for NFSv4 (the RFC for NFSv4
specifies the "share_deny" field within the NFS open request, and
various clients, but not Linux, set it), and would allow WINE to
function properly over a network mount.
>we proffer to add into the file /usr/include/asm-generic/fcntl.h
> following flags:
>
>#define O_DENYREAD 004000000 /* Do not permit read access */
>#define O_DENYWRITE 010000000 /* Do not permit write access */
>#define O_DENYDELETE 020000000 /* Do not permit delete or rename
> operations*/
Presumably for applications on local mounts, wine mediates their own
mandatory locks, but this is impossible on network mounts without this
change (and can lead to data corruption).
--
Thanks,
Steve
next reply other threads:[~2008-12-02 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 16:31 Steve French [this message]
2008-12-02 19:38 ` Support for applications which need NFS or CIFS "share_deny" flags on open Andreas Dilger
2008-12-02 20:06 ` Jamie Lokier
2008-12-02 20:20 ` Steve French
2008-12-02 20:21 ` Steve French
2008-12-02 21:20 ` jim owens
2008-12-02 21:26 ` Steve French
2008-12-02 23:07 ` Jeremy Allison
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=524f69650812020831q4e089b87k9a8306ac37f4234a@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).