linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Shilovsky <piastry-7qunaywFIewox3rIn2DAYQ@public.gmane.org>
To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	wine-devel-5vRYHf7vrtgdnm+yROfE0A@public.gmane.org
Subject: [PATCH v2 0/8] Add O_DENY* support for VFS and CIFS/NFS
Date: Thu, 17 Jan 2013 20:52:09 +0400	[thread overview]
Message-ID: <1358441537-8672-1-git-send-email-piastry@etersoft.ru> (raw)

This patchset adds support of O_DENY* flags for Linux fs layer. These flags can be used by any application that needs share reservations to organize a file access. VFS already has some sort of this capability - now it's done through flock/LOCK_MAND mechanis, but that approach is non-atomic. This patchset build new capabilities on top of the existing one but doesn't bring any changes into the flock call semantic.

These flags can be used by NFS (built-in-kernel) and CIFS (Samba) servers and Wine applications through VFS (for local filesystems) or CIFS/NFS modules. This will help when e.g. Samba and NFS server share the same directory for Windows and Linux users or Wine applications use Samba/NFS share to access the same data from different clients.

According to the previous discussions the most problematic question is how to prevent situations like DoS attacks where e.g /lib/liba.so file can be open with DENYREAD, or smth like this. That's why one extra flag O_DENYMAND is added. It indicates to underlying layer that an application want to use O_DENY* flags semantic. It allows us not affect native Linux applications (that don't use O_DENYMAND flag) - so, these flags (and the semantic of open syscall that they bring) are used only for those applications that really want it proccessed that way.

So, we have four new flags:
O_DENYREAD - to prevent other opens with read access,
O_DENYWRITE - to prevent other opens with write access,
O_DENYDELETE - to prevent delete operations (this flag is not implemented in VFS and NFS part and only suitable for CIFS module),
O_DENYMAND - to switch on/off three flags above.

The #1 patch bring infrastructure to let us add this capability easier. #2 patch adds flags to fcntl while #3 patch implement VFS part. Patches #4, #5, #6 are related to CIFS-specific changes. #7 and #8 describe NFS and NFSD parts.

Also, I created the preliminary patch for Samba that replaces the existing use of flock/LOCK_MAND mechanism with O_DENY* flags:
http://git.etersoft.ru/people/piastry/packages/?p=samba.git;a=commitdiff;h=f116c478bf9a1bc3985e9a719fb20d854914d67a

Pavel Shilovsky (8):
  locks: make flock_lock_file take is_conflict callback parm
  fcntl: Introduce new O_DENY* open flags
  vfs: Add O_DENYREAD/WRITE flags support for open syscall
  CIFS: Add O_DENY* open flags support
  CIFS: Use NT_CREATE_ANDX command for forcemand mounts
  CIFS: Translate SHARING_VIOLATION to -ETXTBSY error code for SMB2
  NFSv4: Add O_DENY* open flags support
  NFSD: Pass share reservations flags to VFS

 fs/cifs/cifsacl.c                |  10 ++--
 fs/cifs/cifsglob.h               |  12 +++-
 fs/cifs/cifsproto.h              |   9 +--
 fs/cifs/cifssmb.c                |  47 ++++++++-------
 fs/cifs/dir.c                    |  14 +++--
 fs/cifs/file.c                   |  18 ++++--
 fs/cifs/inode.c                  |  11 ++--
 fs/cifs/link.c                   |  10 ++--
 fs/cifs/readdir.c                |   2 +-
 fs/cifs/smb1ops.c                |  15 ++---
 fs/cifs/smb2file.c               |  10 ++--
 fs/cifs/smb2inode.c              |   4 +-
 fs/cifs/smb2maperror.c           |   2 +-
 fs/cifs/smb2ops.c                |  10 ++--
 fs/cifs/smb2pdu.c                |   6 +-
 fs/cifs/smb2proto.h              |  14 +++--
 fs/fcntl.c                       |   5 +-
 fs/locks.c                       | 121 ++++++++++++++++++++++++++++++++++++---
 fs/namei.c                       |  10 +++-
 fs/nfs/nfs4xdr.c                 |  24 ++++++--
 fs/nfsd/nfs4state.c              |  46 ++++++++++++++-
 include/linux/fs.h               |   6 ++
 include/uapi/asm-generic/fcntl.h |  14 +++++
 23 files changed, 324 insertions(+), 96 deletions(-)

-- 
1.8.1.1

             reply	other threads:[~2013-01-17 16:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17 16:52 Pavel Shilovsky [this message]
     [not found] ` <1358441537-8672-1-git-send-email-piastry-7qunaywFIewox3rIn2DAYQ@public.gmane.org>
2013-01-17 22:55   ` [PATCH v2 0/8] Add O_DENY* support for VFS and CIFS/NFS Stephen Rothwell
2013-01-18  6:29     ` Pavel Shilovsky
2013-01-30 22:11   ` J. Bruce Fields
     [not found]     ` <20130130221118.GB15584-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2013-02-05 11:33       ` Pavel Shilovsky
     [not found]         ` <CAKywueQcia1jJfdVJFzfHdc5zQ_86r3T4bmee9cpP18qqbcLFA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-05 14:38           ` J. Bruce Fields
     [not found]             ` <20130205143813.GB9886-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2013-02-07  9:40               ` 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=1358441537-8672-1-git-send-email-piastry@etersoft.ru \
    --to=piastry-7qunaywfiewox3rin2dayq@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=wine-devel-5vRYHf7vrtgdnm+yROfE0A@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).