From: Pavel Shilovsky <piastry@etersoft.ru>
To: linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/2] Shared flags
Date: Mon, 10 Nov 2008 16:58:17 +0300 [thread overview]
Message-ID: <49183DF9.9010003@etersoft.ru> (raw)
Hello!
We have situation during our work with Wine and Cifs-client then we
have to use sharing access policy to files and we used 3 free bits from
21 to 23 of attribute flag(it allows to do NT-semantic for opening files
in open() and it is necessary for correct implementation of function
NTCreateFile in Wine). We think that it'll be useful not only for us and
we proffer to add into the file kernel/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*/
Yes, it'll change semantic of calling open() function, but by default(if
not to use these flags) functionality won't changed, and if we use it
we'll acquire new resources for organization file access policy. On the
other hand, we patched cifs with inverting these flags, because
according to CIFS protocol
#define FILE_SHARE_ALL 0x00000007
ones have opposite meaning.
Summary of changes:
[1/2] patch added share flags in kernel/include/asm-generic/fcntl.h
[2/2] patch added the use of share flags in cifs client
Here is a public git repository
http://git.etersoft.ru/people/kipruss/packages/?p=cifs-2.6.git;a=shortlog;h=refs/heads/etersoft-to-kernel
Yours faithfully,
Pavel Shilovsky.
next reply other threads:[~2008-11-10 13:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 13:58 Pavel Shilovsky [this message]
[not found] ` <49183DF9.9010003-7qunaywFIewox3rIn2DAYQ@public.gmane.org>
2008-11-11 8:52 ` [PATCH 0/2] Shared flags Christoph Hellwig
2008-11-11 10:09 ` Jamie Lokier
2008-11-11 11:14 ` Christoph Hellwig
2008-11-13 10:08 ` Pavel Shilovsky
[not found] ` <491BFCBA.80208-7qunaywFIewox3rIn2DAYQ@public.gmane.org>
2008-11-13 9:25 ` Christoph Hellwig
2008-11-14 3:37 ` Jamie Lokier
2008-11-15 11:39 ` Christoph Hellwig
2008-11-16 5:57 ` Pavel Shilovsky
[not found] ` <20081113092554.GA3004-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2008-11-16 10:37 ` Benny Halevy
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=49183DF9.9010003@etersoft.ru \
--to=piastry@etersoft.ru \
--cc=linux-fsdevel@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).