From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753207AbdHQQXs (ORCPT ); Thu, 17 Aug 2017 12:23:48 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:41326 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752857AbdHQQXr (ORCPT ); Thu, 17 Aug 2017 12:23:47 -0400 Date: Thu, 17 Aug 2017 09:23:48 -0700 From: Greg Kroah-Hartman To: James Simmons Cc: devel@driverdev.osuosl.org, Andreas Dilger , Oleg Drokin , Robin Humble , Linux Kernel Mailing List , Lustre Development List Subject: Re: [PATCH v2 01/14] staging: lustre: llite: Remove filtering of seclabel xattr Message-ID: <20170817162348.GA22834@kroah.com> References: <1502727664-29438-1-git-send-email-jsimmons@infradead.org> <1502727664-29438-2-git-send-email-jsimmons@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1502727664-29438-2-git-send-email-jsimmons@infradead.org> User-Agent: Mutt/1.8.3 (2017-05-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Aug 14, 2017 at 12:20:51PM -0400, James Simmons wrote: > From: Robin Humble > > 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. > > Signed-off-by: Robin Humble > Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9562 > Reviewed-on: https://review.whamcloud.com/27292 > Reviewed-by: John L. Hammond > Reviewed-by: Sebastien Buisson > Reviewed-by: Oleg Drokin > Signed-off-by: James Simmons > --- > Changelog: > > v1) Initial submit with wrong patch attached. > v2) Proper patch this time. I don't see a v1 patch anywhere... Anyway, when you do this, please make your subject such that I can sort the emails properly and they show up in the correct order, so put the "v2" after the patch number like this: Subject: [PATCH 01/14 v2] staging: lustre: llite: Remove filtering of I think git does that correctly for you automatically if you use it... thanks, greg k-h