linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruenba-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Alexander Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
Cc: Andreas Gruenbacher
	<agruenba-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Miklos Szeredi <mszeredi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
	Theodore Ts'o <tytso-3s7WtUTddSA@public.gmane.org>,
	Andreas Dilger
	<adilger.kernel-m1MBpc4rdrD3fQ9qLvQP4Q@public.gmane.org>,
	"J. Bruce Fields"
	<bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>,
	Jeff Layton <jlayton-vpEMnDpepFuMZCB2o+C8xQ@public.gmane.org>,
	Trond Myklebust
	<trond.myklebust-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>,
	Anna Schumaker
	<anna.schumaker-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>,
	Dave Chinner <david-FqsqvQoI3Ljby3iVrkZq2A@public.gmane.org>,
	linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-xfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH v28 00/21] Richacls (Core and Ext4)
Date: Mon, 13 Feb 2017 16:32:16 +0100	[thread overview]
Message-ID: <1486999957-2381-1-git-send-email-agruenba@redhat.com> (raw)

Here is another update of the richacl patches.  Changes since the last posting
(https://lwn.net/Articles/703199/):

 * Fix permission checking for file exchange (i.e., renameat2 with the
   RENAME_EXCHANGE flag): in some cases, the MAY_CREATE_FILE and MAY_CREATE_DIR
   permissions were swapped.

   This should have been caught by the test suite but wasn't.  Meanwhile the
   test suite is fixed as well.

 * When deleting a file and we have MAY_DELETE_SELF permission on the file, we
   don't require MAY_DELETE_CHILD permission on the containing directory.
   However, we must still call inode_permission with MAY_WRITE in mask for
   checks beyond file permission bits or ACLs, such as LSM.


Many thanks to Miklos for the previous patch review.


The complete patch queue is available here:

  git://git.kernel.org/pub/scm/linux/kernel/git/agruen/linux-richacl.git \
	richacl-2017-02-13


The richacl user-space utilitites, man pages, and test suite are available
here:

  https://github.com/andreas-gruenbacher/richacl


Changes to other user-space packages for richacl:

  https://github.com/andreas-gruenbacher/coreutils
  https://github.com/andreas-gruenbacher/e2fsprogs
  https://github.com/andreas-gruenbacher/samba
  https://github.com/andreas-gruenbacher/xfsprogs-dev
  https://github.com/andreas-gruenbacher/nfs-utils


Please see the richacl homepage for more information:

  http://www.bestbits.at/richacl/


Thanks,
Andreas

Andreas Gruenbacher (19):
  vfs: Add IS_ACL() and IS_RICHACL() tests
  vfs: Add MAY_CREATE_FILE and MAY_CREATE_DIR permission flags
  vfs: Add MAY_DELETE_SELF and MAY_DELETE_CHILD permission flags
  vfs: Add permission flags for setting file attributes
  richacl: In-memory representation and helper functions
  richacl: Permission mapping functions
  richacl: Permission check algorithm
  richacl: Compute maximum file masks from an acl
  vfs: Cache base_acl objects in inodes
  vfs: Add get_richacl and set_richacl inode operations
  vfs: Cache richacl in struct inode
  richacl: Update the file masks in chmod()
  richacl: Check if an acl is equivalent to a file mode
  richacl: Create-time inheritance
  richacl: Automatic Inheritance
  richacl: xattr mapping functions
  richacl: Add richacl xattr handler
  vfs: Add richacl permission checking
  vfs: Move check_posix_acl and check_richacl out of fs/namei.c

Aneesh Kumar K.V (2):
  ext4: Add richacl support
  ext4: Add richacl feature flag

 fs/9p/acl.c                        |   8 +-
 fs/Kconfig                         |   3 +
 fs/Makefile                        |   1 +
 fs/attr.c                          |  79 +++-
 fs/ext4/Kconfig                    |  11 +
 fs/ext4/Makefile                   |   1 +
 fs/ext4/ext4.h                     |   7 +-
 fs/ext4/file.c                     |   3 +
 fs/ext4/ialloc.c                   |  11 +-
 fs/ext4/inode.c                    |   4 +-
 fs/ext4/namei.c                    |   5 +
 fs/ext4/richacl.c                  | 134 ++++++
 fs/ext4/richacl.h                  |  40 ++
 fs/ext4/super.c                    |  48 +-
 fs/ext4/xattr.c                    |   7 +
 fs/f2fs/acl.c                      |   4 +-
 fs/inode.c                         |  43 +-
 fs/jffs2/acl.c                     |   6 +-
 fs/namei.c                         | 150 +++---
 fs/nfs/nfs3acl.c                   |  14 +-
 fs/posix_acl.c                     |  97 ++--
 fs/richacl.c                       | 937 +++++++++++++++++++++++++++++++++++++
 fs/richacl_xattr.c                 | 222 +++++++++
 include/linux/acl.h                |  15 +
 include/linux/fs.h                 |  58 ++-
 include/linux/posix_acl.h          |  24 +-
 include/linux/richacl.h            | 218 +++++++++
 include/linux/richacl_xattr.h      |  31 ++
 include/uapi/linux/Kbuild          |   2 +
 include/uapi/linux/fs.h            |   3 +-
 include/uapi/linux/richacl.h       | 152 ++++++
 include/uapi/linux/richacl_xattr.h |  44 ++
 include/uapi/linux/xattr.h         |   2 +
 33 files changed, 2216 insertions(+), 168 deletions(-)
 create mode 100644 fs/ext4/richacl.c
 create mode 100644 fs/ext4/richacl.h
 create mode 100644 fs/richacl.c
 create mode 100644 fs/richacl_xattr.c
 create mode 100644 include/linux/acl.h
 create mode 100644 include/linux/richacl.h
 create mode 100644 include/linux/richacl_xattr.h
 create mode 100644 include/uapi/linux/richacl.h
 create mode 100644 include/uapi/linux/richacl_xattr.h

-- 
2.7.4

--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" 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:[~2017-02-13 15:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-13 15:32 Andreas Gruenbacher [this message]
2017-02-13 15:32 ` [PATCH v28 01/21] vfs: Add IS_ACL() and IS_RICHACL() tests Andreas Gruenbacher
2017-02-13 15:32 ` [PATCH v28 02/21] vfs: Add MAY_CREATE_FILE and MAY_CREATE_DIR permission flags Andreas Gruenbacher
2017-02-13 15:32 ` [PATCH v28 03/21] vfs: Add MAY_DELETE_SELF and MAY_DELETE_CHILD " Andreas Gruenbacher
2017-02-13 15:32 ` [PATCH v28 04/21] vfs: Add permission flags for setting file attributes Andreas Gruenbacher
2017-02-13 15:32 ` [PATCH v28 05/21] richacl: In-memory representation and helper functions Andreas Gruenbacher
2017-02-13 15:32 ` [PATCH v28 06/21] richacl: Permission mapping functions Andreas Gruenbacher
2017-02-13 15:32 ` [PATCH v28 07/21] richacl: Permission check algorithm Andreas Gruenbacher
2017-02-13 15:32 ` [PATCH v28 08/21] richacl: Compute maximum file masks from an acl Andreas Gruenbacher
     [not found] ` <1486999957-2381-1-git-send-email-agruenba-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-02-13 15:32   ` [PATCH v28 09/21] vfs: Cache base_acl objects in inodes Andreas Gruenbacher
2017-02-13 15:32   ` [PATCH v28 10/21] vfs: Add get_richacl and set_richacl inode operations Andreas Gruenbacher
2017-02-13 15:32   ` [PATCH v28 12/21] richacl: Update the file masks in chmod() Andreas Gruenbacher
2017-02-13 15:32   ` [PATCH v28 18/21] vfs: Add richacl permission checking Andreas Gruenbacher
2017-02-13 15:32   ` [PATCH v28 19/21] vfs: Move check_posix_acl and check_richacl out of fs/namei.c Andreas Gruenbacher
2017-02-13 15:32 ` [PATCH v28 11/21] vfs: Cache richacl in struct inode Andreas Gruenbacher
2017-02-13 15:32 ` [PATCH v28 13/21] richacl: Check if an acl is equivalent to a file mode Andreas Gruenbacher
2017-02-13 15:32 ` [PATCH v28 14/21] richacl: Create-time inheritance Andreas Gruenbacher
2017-02-13 15:32 ` [PATCH v28 15/21] richacl: Automatic Inheritance Andreas Gruenbacher
2017-02-13 15:32 ` [PATCH v28 16/21] richacl: xattr mapping functions Andreas Gruenbacher
2017-02-13 15:32 ` [PATCH v28 17/21] richacl: Add richacl xattr handler Andreas Gruenbacher
2017-02-13 15:32 ` [PATCH v28 20/21] ext4: Add richacl support Andreas Gruenbacher
2017-02-13 15:32 ` [PATCH v28 21/21] ext4: Add richacl feature flag Andreas Gruenbacher

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=1486999957-2381-1-git-send-email-agruenba@redhat.com \
    --to=agruenba-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=adilger.kernel-m1MBpc4rdrD3fQ9qLvQP4Q@public.gmane.org \
    --cc=anna.schumaker-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org \
    --cc=bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org \
    --cc=david-FqsqvQoI3Ljby3iVrkZq2A@public.gmane.org \
    --cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=jlayton-vpEMnDpepFuMZCB2o+C8xQ@public.gmane.org \
    --cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-ext4-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=linux-xfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mszeredi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=trond.myklebust-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org \
    --cc=tytso-3s7WtUTddSA@public.gmane.org \
    --cc=viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@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).