> On Mon, Aug 14, 2017 at 12:20:51PM -0400, James Simmons wrote: > > From: Robin Humble <plaguedbypenguins@xxxxxxxxx> > > > > 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 <plaguedbypenguins@xxxxxxxxx> > > Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-9562 > > Reviewed-on: https://review.whamcloud.com/27292 > > Reviewed-by: John L. Hammond <john.hammond@xxxxxxxxx> > > Reviewed-by: Sebastien Buisson <sbuisson@xxxxxxx> > > Reviewed-by: Oleg Drokin <oleg.drokin@xxxxxxxxx> > > Signed-off-by: James Simmons <jsimmons@xxxxxxxxxxxxx> > > --- > > Changelog: > > > > v1) Initial submit with wrong patch attached. > > v2) Proper patch this time. > > I don't see a v1 patch anywhere... Its the patch I asked you to drop earlier. Same commit message but I mixed up the patch with another patch. > 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... Will do. _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
