From: NeilBrown <neilb@suse.com>
To: Oleg Drokin <oleg.drokin@intel.com>,
Andreas Dilger <andreas.dilger@intel.com>,
James Simmons <jsimmons@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
lustre <lustre-devel@lists.lustre.org>
Subject: [PATCH SERIES 2: 0/4] staging:lustre: improve mounting code
Date: Mon, 18 Dec 2017 12:13:20 +1100 [thread overview]
Message-ID: <151355938405.10227.11903161187102828189.stgit@noble> (raw)
These patches make improvements to the lustre code
for supporting the mount system call.
There is a user-visible change: "lustre" now appears in
/proc/filesystem with the "nodev" flag present. Previously
it didn't have this flag, which was incorrect.
There is also a bugfix: there is a possible module-unload race
that could trigger a crash.
Thanks,
NeilBrown
---
NeilBrown (4):
staging: lustre: obdclass: discard FS_NEEDS_DEV flag.
staging: lustre: obdclass: remove pointless struct lustre_mount_data2
staging: lustre: obdclass: remove vfsmount option from client_fill_super
staging: lustre: obd_mount: fix possible race with module unload.
.../staging/lustre/lustre/include/lustre_disk.h | 6 +-
.../staging/lustre/lustre/llite/llite_internal.h | 2 -
drivers/staging/lustre/lustre/llite/llite_lib.c | 7 +-
drivers/staging/lustre/lustre/llite/super25.c | 6 +-
drivers/staging/lustre/lustre/obdclass/obd_mount.c | 63 +++++++++-----------
5 files changed, 38 insertions(+), 46 deletions(-)
--
Signature
next reply other threads:[~2017-12-18 1:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 1:13 NeilBrown [this message]
2017-12-18 1:13 ` [PATCH 1/4] staging: lustre: obdclass: discard FS_NEEDS_DEV flag NeilBrown
2017-12-18 1:13 ` [PATCH 3/4] staging: lustre: obdclass: remove vfsmount option from client_fill_super NeilBrown
2017-12-18 1:13 ` [PATCH 2/4] staging: lustre: obdclass: remove pointless struct lustre_mount_data2 NeilBrown
2017-12-18 1:13 ` [PATCH 4/4] staging: lustre: obd_mount: fix possible race with module unload NeilBrown
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=151355938405.10227.11903161187102828189.stgit@noble \
--to=neilb@suse.com \
--cc=andreas.dilger@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--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
all inboxes | Powered by JetHome®