From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: James Simmons <jsimmons@infradead.org>
Cc: devel@driverdev.osuosl.org,
Andreas Dilger <andreas.dilger@intel.com>,
Oleg Drokin <oleg.drokin@intel.com>,
Robin Humble <plaguedbypenguins@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lustre Development List <lustre-devel@lists.lustre.org>
Subject: Re: [PATCH 18/20] staging: lustre: llite: Remove filtering of seclabel xattr
Date: Sun, 30 Jul 2017 08:04:25 -0700 [thread overview]
Message-ID: <20170730150425.GA25625@kroah.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1707272034380.6670@casper.infradead.org>
On Thu, Jul 27, 2017 at 08:35:33PM +0100, James Simmons wrote:
>
> > From: Robin Humble <plaguedbypenguins@gmail.com>
> >
> > The security.capability xattr is used to implement File
> > Capabilities in recent Linux versions. Capabilities are a
> > fine grained approach to granting executables elevated
> > privileges. eg. /bin/ping can have capabilities
> > cap_net_admin, cap_net_raw+ep instead of being setuid root.
> >
> > This xattr has long been filtered out by llite, initially for
> > stability reasons (b15587), and later over performance
> > concerns as this xattr is read for every file with eg.
> > 'ls --color'. Since LU-2869 xattr's are cached on clients,
> > alleviating most performance concerns.
> >
> > Removing llite's filtering of the security.capability xattr
> > enables using Lustre as a root filesystem, which is used on
> > some large clusters.
>
> The commit message for this patch is incorrect. Some how it got
> mixed up with another patch which I missed in this push. Please
> drop this patch and I will resent the correct patches later.
Now dropped.
next prev parent reply other threads:[~2017-07-30 17:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 15:22 [PATCH 00/20] staging: lustre: batch of fixes to decrease test failures James Simmons
2017-07-26 15:22 ` [PATCH 01/20] staging: lustre: osc: soft lock - osc_makes_rpc() James Simmons
2017-07-26 15:22 ` [PATCH 02/20] staging: lustre: ldlm: restore missing newlines in ldlm sysfs files James Simmons
2017-07-26 15:22 ` [PATCH 03/20] staging: lustre: ldlm: crash on umount in cleanup_resource James Simmons
2017-07-26 15:22 ` [PATCH 04/20] staging: lustre: lov: fix 'control flow' error in lov_io_init_released James Simmons
2017-07-26 15:22 ` [PATCH 05/20] staging: lustre: lov: remove unused code James Simmons
2017-07-26 15:22 ` [PATCH 06/20] staging: lustre: lmv: assume a real connection in lmv_connect() James Simmons
2017-07-26 15:22 ` [PATCH 07/20] staging: lustre: lov: Ensure correct operation for large object sizes James Simmons
2017-07-26 15:22 ` [PATCH 08/20] staging: lustre: ptlrpc: correct use of list_add_tail() James Simmons
2017-07-26 15:22 ` [PATCH 09/20] staging: lustre: ptlrpc: no need to reassign mbits for replay James Simmons
2017-07-26 15:22 ` [PATCH 10/20] staging: lustre: ldlm: restore interval_iterate_reverse function James Simmons
2017-07-26 15:22 ` [PATCH 11/20] staging: lustre: lustre: fix all less than 0 comparison for unsigned values James Simmons
2017-07-26 15:22 ` [PATCH 12/20] staging: lustre: linkea: linkEA size limitation James Simmons
2017-07-26 15:22 ` [PATCH 13/20] staging: lustre: ptlrpc: restore 64-bit time for struct ptlrpc_cli_req James Simmons
2017-07-26 15:22 ` [PATCH 14/20] staging: lustre: ptlrpc: don't use CFS_DURATION_T for time64_t James Simmons
2017-07-26 15:22 ` [PATCH 15/20] staging: lustre: ptlrpc: print times in microseconds James Simmons
2017-07-26 15:22 ` [PATCH 16/20] staging: lustre: libcfs: fix test for libcfs_ioctl_hdr minimum size James Simmons
2017-07-26 15:22 ` [PATCH 17/20] staging: lustre: llite: allow cached acls James Simmons
2017-07-26 15:22 ` [PATCH 18/20] staging: lustre: llite: Remove filtering of seclabel xattr James Simmons
2017-07-27 19:35 ` James Simmons
2017-07-30 15:04 ` Greg Kroah-Hartman [this message]
2017-07-26 15:22 ` [PATCH 19/20] staging: lustre: llite: add xattr.h header to xattr.c James Simmons
2017-07-26 15:22 ` [PATCH 20/20] staging: lustre: llite: set security xattr using __vfs_setxattr James Simmons
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=20170730150425.GA25625@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=oleg.drokin@intel.com \
--cc=plaguedbypenguins@gmail.com \
/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