From: green@linuxhacker.ru
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org,
Andreas Dilger <andreas.dilger@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Oleg Drokin <green@linuxhacker.ru>
Subject: [PATCH 00/10] Lustre fixes
Date: Wed, 25 Mar 2015 21:53:16 -0400 [thread overview]
Message-ID: <1427334806-31466-1-git-send-email-green@linuxhacker.ru> (raw)
From: Oleg Drokin <green@linuxhacker.ru>
A number of lustre fixes.
Andriy Skulysh (1):
staging/lustre/ptlrpc: fix import state during replay
Bobi Jam (2):
staging/lustre/osc: shorten IO calling path
staging/lustre/mgc: detach MGC dev on error
Christopher J. Morrone (1):
staging/lustre/mdc: Handle empty but non-zero acl xattr
Hongchao Zhang (1):
staging/lustre/mgc: check the import stat for lprocfs
Lai Siyao (1):
staging/lustre/xattr: xattr data may be gone with lock held
Li Dongyang (1):
staging/lustre/llite: glimpse the inode before doing fiemap
Liang Zhen (1):
staging/lustre/ptlrpc: false alarm in AT network latency measuring
Niu Yawei (1):
staging/lustre: update timestamps after buiding rpc
Yang Sheng (1):
staging/lustre/lov: don't crash accessing LOV object with FID{0,0}
.../staging/lustre/lustre/include/lustre_import.h | 2 +
drivers/staging/lustre/lustre/llite/file.c | 6 +++
drivers/staging/lustre/lustre/llite/xattr_cache.c | 19 +++++----
drivers/staging/lustre/lustre/lov/lov_ea.c | 6 +++
drivers/staging/lustre/lustre/lov/lov_internal.h | 12 ++++++
drivers/staging/lustre/lustre/lov/lov_io.c | 12 ++++++
drivers/staging/lustre/lustre/lov/lov_lock.c | 26 ++++++++++---
drivers/staging/lustre/lustre/lov/lov_obd.c | 32 ++++++++++++---
drivers/staging/lustre/lustre/lov/lov_object.c | 7 ++++
drivers/staging/lustre/lustre/lov/lov_request.c | 9 +++++
drivers/staging/lustre/lustre/mdc/mdc_request.c | 3 ++
drivers/staging/lustre/lustre/mgc/mgc_request.c | 45 +++++++++++++++-------
drivers/staging/lustre/lustre/osc/osc_cache.c | 2 +-
drivers/staging/lustre/lustre/osc/osc_request.c | 3 ++
drivers/staging/lustre/lustre/ptlrpc/client.c | 25 +++++++++---
drivers/staging/lustre/lustre/ptlrpc/import.c | 15 +++++++-
16 files changed, 184 insertions(+), 40 deletions(-)
--
2.1.0
next reply other threads:[~2015-03-26 1:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 1:53 green [this message]
2015-03-26 1:53 ` [PATCH 01/10] staging/lustre/osc: shorten IO calling path green
2015-03-26 2:04 ` [PATCH v2 " green
2015-03-26 10:09 ` Greg Kroah-Hartman
2015-03-26 1:53 ` [PATCH 02/10] staging/lustre/mdc: Handle empty but non-zero acl xattr green
2015-03-26 1:53 ` [PATCH 03/10] staging/lustre/ptlrpc: false alarm in AT network latency measuring green
2015-03-26 1:53 ` [PATCH 04/10] staging/lustre/mgc: check the import stat for lprocfs green
2015-03-26 1:53 ` [PATCH 05/10] staging/lustre/mgc: detach MGC dev on error green
2015-03-26 1:53 ` [PATCH 06/10] staging/lustre/lov: don't crash accessing LOV object with FID{0,0} green
2015-03-26 1:53 ` [PATCH 07/10] staging/lustre/ptlrpc: fix import state during replay green
2015-03-26 2:07 ` [PATCH v2 " green
2015-03-26 1:53 ` [PATCH 08/10] staging/lustre/llite: glimpse the inode before doing fiemap green
2015-03-26 1:53 ` [PATCH 09/10] staging/lustre: update timestamps after buiding rpc green
2015-03-26 1:53 ` [PATCH 10/10] staging/lustre/xattr: xattr data may be gone with lock held green
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=1427334806-31466-1-git-send-email-green@linuxhacker.ru \
--to=green@linuxhacker.ru \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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).