From: James Simmons <jsimmons@infradead.org>
To: Andreas Dilger <adilger@whamcloud.com>,
Oleg Drokin <green@whamcloud.com>, NeilBrown <neilb@suse.de>
Cc: Lustre Development List <lustre-devel@lists.lustre.org>
Subject: [lustre-devel] [PATCH 0/9] Sync to OpenSFS as of Feb 8, 2021
Date: Mon, 8 Feb 2021 19:54:18 -0500 [thread overview]
Message-ID: <1612832067-1449-1-git-send-email-jsimmons@infradead.org> (raw)
Bring the Linux client up to date with the OpenSFS branch as of
Feb 8, 2021
Andreas Dilger (2):
lustre: llite: send file mode with rename RPC
lustre: osc: avoid crash if ocd reset
Bobi Jam (1):
lustre: osc: correctly update size/kms for fallocate
Emoly Liu (1):
lustre: lov: return stripe_count=1 instead of 0 for DoM files
Mikhail Pershin (1):
lustre: ldlm: don't change GROUP lock GID on client
Qian Yingjin (1):
lustre: flr: skip unknown FLR component types
Sebastien Buisson (1):
lustre: sec: get rid of bad rss-counter state messages
Wang Shilong (1):
lustre: obdclass: connect vs disconnect race
Yang Sheng (1):
lustre: obdclass: add option %H for jobid
fs/lustre/include/cl_object.h | 6 +++
fs/lustre/include/lustre_crypto.h | 8 +++
fs/lustre/include/obd.h | 8 +--
fs/lustre/ldlm/ldlm_inodebits.c | 5 +-
fs/lustre/llite/namei.c | 9 +++-
fs/lustre/llite/rw26.c | 23 ++-------
fs/lustre/llite/vvp_io.c | 2 +-
fs/lustre/lov/lov_cl_internal.h | 7 ++-
fs/lustre/lov/lov_ea.c | 66 ++++++++++++++++++------
fs/lustre/lov/lov_internal.h | 15 +++++-
fs/lustre/lov/lov_io.c | 25 ++++++---
fs/lustre/lov/lov_object.c | 22 +++++++-
fs/lustre/lov/lov_pack.c | 8 +++
fs/lustre/obdclass/cl_io.c | 11 ----
fs/lustre/obdclass/cl_page.c | 1 +
fs/lustre/obdclass/jobid.c | 13 ++++-
fs/lustre/obdclass/obd_config.c | 4 --
fs/lustre/osc/osc_cache.c | 3 +-
fs/lustre/osc/osc_io.c | 33 ++++++------
fs/lustre/osc/osc_object.c | 4 +-
fs/lustre/osc/osc_request.c | 89 ++++++++++++++++++++++++++-------
include/uapi/linux/lustre/lustre_user.h | 1 +
22 files changed, 258 insertions(+), 105 deletions(-)
--
1.8.3.1
_______________________________________________
lustre-devel mailing list
lustre-devel@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
next reply other threads:[~2021-02-09 0:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 0:54 James Simmons [this message]
2021-02-09 0:54 ` [lustre-devel] [PATCH 1/9] lustre: llite: send file mode with rename RPC James Simmons
2021-02-09 0:54 ` [lustre-devel] [PATCH 2/9] lustre: flr: skip unknown FLR component types James Simmons
2021-02-09 0:54 ` [lustre-devel] [PATCH 3/9] lustre: obdclass: connect vs disconnect race James Simmons
2021-02-09 0:54 ` [lustre-devel] [PATCH 4/9] lustre: osc: correctly update size/kms for fallocate James Simmons
2021-02-09 0:54 ` [lustre-devel] [PATCH 5/9] lustre: ldlm: don't change GROUP lock GID on client James Simmons
2021-02-09 0:54 ` [lustre-devel] [PATCH 6/9] lustre: sec: get rid of bad rss-counter state messages James Simmons
2021-02-09 0:54 ` [lustre-devel] [PATCH 7/9] lustre: obdclass: add option %H for jobid James Simmons
2021-02-09 0:54 ` [lustre-devel] [PATCH 8/9] lustre: osc: avoid crash if ocd reset James Simmons
2021-02-09 0:54 ` [lustre-devel] [PATCH 9/9] lustre: lov: return stripe_count=1 instead of 0 for DoM files 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=1612832067-1449-1-git-send-email-jsimmons@infradead.org \
--to=jsimmons@infradead.org \
--cc=adilger@whamcloud.com \
--cc=green@whamcloud.com \
--cc=lustre-devel@lists.lustre.org \
--cc=neilb@suse.de \
/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).