linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Pavel Shilovsky <piastry-7qunaywFIewox3rIn2DAYQ@public.gmane.org>
Cc: linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 0/2] Shared flags
Date: Tue, 11 Nov 2008 03:52:11 -0500	[thread overview]
Message-ID: <20081111085211.GB2323@infradead.org> (raw)
In-Reply-To: <49183DF9.9010003-7qunaywFIewox3rIn2DAYQ@public.gmane.org>

On Mon, Nov 10, 2008 at 04:58:17PM +0300, Pavel Shilovsky wrote:
> 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*/

I'm not completely opposed to these, but the patches you postd are
rather incomplete:

 (1) you need to add it to fcntl.h for those architetures not using the
     generic fcntl.h or those who would have overlapping bits with the
     generic defintions.
 (2) you also need to enforce these semantics in the VFS for local
     filesystems

Now if (2) doesn't cause too much overhead I would say it's fine, if not
I would rather avoid it.

Also please Cc the linux-api list for userspace API updates.

--
To unsubscribe from this list: send the line "unsubscribe linux-api" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

       reply	other threads:[~2008-11-11  8:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49183DF9.9010003@etersoft.ru>
     [not found] ` <49183DF9.9010003-7qunaywFIewox3rIn2DAYQ@public.gmane.org>
2008-11-11  8:52   ` Christoph Hellwig [this message]
2008-11-11 10:09     ` [PATCH 0/2] Shared flags 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
     [not found]                   ` <20081115113938.GA26576-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
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=20081111085211.GB2323@infradead.org \
    --to=hch-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
    --cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=piastry-7qunaywFIewox3rIn2DAYQ@public.gmane.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).