LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: James Simmons <jsimmons@infradead.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org,
Andreas Dilger <andreas.dilger@intel.com>,
Oleg Drokin <oleg.drokin@intel.com>, NeilBrown <neilb@suse.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lustre Development List <lustre-devel@lists.lustre.org>
Subject: [PATCH 0/5] staging: lustre: llite: remaining xattr fixes
Date: Mon, 14 May 2018 22:16:58 -0400 [thread overview]
Message-ID: <1526350623-4616-1-git-send-email-jsimmons@infradead.org> (raw)
Fixed the bugs in the set_acl patch pointed out by Dan Carpenter.
Rebased the next patch 'remove unused parameter..." on the parent
patch. Added newer xattr fixes that were recently pushed.
Andrew Perepechko (1):
staging: lustre: mdc: excessive memory consumption by the xattr cache
Dmitry Eremin (1):
staging: lustre: llite: add support set_acl method in inode operations
Fan Yong (1):
staging: lustre: acl: increase ACL entries limitation
John L. Hammond (2):
staging: lustre: llite: remove unused parameters from md_{get,set}xattr()
staging: lustre: mdc: use large xattr buffers for old servers
.../lustre/include/uapi/linux/lustre/lustre_idl.h | 2 +-
drivers/staging/lustre/lustre/include/lustre_acl.h | 7 ++-
drivers/staging/lustre/lustre/include/obd.h | 7 +--
drivers/staging/lustre/lustre/include/obd_class.h | 21 +++----
drivers/staging/lustre/lustre/llite/file.c | 65 +++++++++++++++++++++-
.../staging/lustre/lustre/llite/llite_internal.h | 4 ++
drivers/staging/lustre/lustre/llite/llite_lib.c | 3 +-
drivers/staging/lustre/lustre/llite/namei.c | 10 +++-
drivers/staging/lustre/lustre/llite/xattr.c | 6 +-
drivers/staging/lustre/lustre/lmv/lmv_obd.c | 22 ++++----
drivers/staging/lustre/lustre/mdc/mdc_locks.c | 42 +++++++++++---
drivers/staging/lustre/lustre/mdc/mdc_reint.c | 2 +
drivers/staging/lustre/lustre/mdc/mdc_request.c | 38 ++++++++-----
drivers/staging/lustre/lustre/ptlrpc/layout.c | 4 +-
drivers/staging/lustre/lustre/ptlrpc/wiretest.c | 4 +-
15 files changed, 171 insertions(+), 66 deletions(-)
--
1.8.3.1
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next reply other threads:[~2018-05-15 2:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 2:16 James Simmons [this message]
2018-05-15 2:16 ` [PATCH v2 1/5] staging: lustre: llite: add support set_acl method in inode operations James Simmons
2018-05-15 3:53 ` NeilBrown
2018-05-15 7:30 ` Greg Kroah-Hartman
2018-05-15 15:01 ` James Simmons
2018-05-15 11:30 ` Dan Carpenter
2018-05-15 15:00 ` James Simmons
2018-05-15 2:17 ` [PATCH v2 2/5] staging: lustre: llite: remove unused parameters from md_{get, set}xattr() James Simmons
2018-05-15 2:17 ` [PATCH 3/5] staging: lustre: acl: increase ACL entries limitation James Simmons
2018-05-15 2:17 ` [PATCH 4/5] staging: lustre: mdc: excessive memory consumption by the xattr cache James Simmons
2018-05-15 2:17 ` [PATCH 5/5] staging: lustre: mdc: use large xattr buffers for old servers 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=1526350623-4616-1-git-send-email-jsimmons@infradead.org \
--to=jsimmons@infradead.org \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=neilb@suse.com \
--cc=oleg.drokin@intel.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;
as well as URLs for NNTP newsgroup(s).