Skip to content

Shared flags

Pavel Shilovsky linux-api linux-fsdevel 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 11 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2Shared flags: fcntl.hinclude/asm-generic/fcntl.h+0 -00 replies
2/2Shared flags: use in cifs clientfs/cifs/cifsacl.c fs/cifs/cifsproto.h fs/cifs/cifssmb.c +6 more+11 -101 reply

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/2] Shared flags

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.