From: Andrew Price <anprice@redhat.com>
To: cluster-devel@redhat.com
Cc: dhowells@redhat.com, linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/2] gfs2: Switch to the new mount API
Date: Sun, 17 Mar 2019 17:40:25 +0000 [thread overview]
Message-ID: <20190317174027.15291-1-anprice@redhat.com> (raw)
These patches convert gfs2 and gfs2meta to use fs_context.
In both cases we still use sget() instead of sget_fc() as there doesn't seem to
be a clear idiomatic way to propagate the bdev currently.
Tested with xfstests -g quick, a bunch of targeted mount commands to exercise
individual options, and gfs2_grow to test the gfs2meta mount.
I'm aiming this at 5.2 so it'll have plenty of soak time.
Thanks to David Howells for providing the method for parsing the complicated
'quota' option.
Andrew Price (2):
gfs2: Convert gfs2 to fs_context
gfs2: Convert gfs2meta to fs_context
fs/gfs2/incore.h | 8 +-
fs/gfs2/ops_fstype.c | 418 +++++++++++++++++++++++++++++++++++++------
fs/gfs2/super.c | 335 +---------------------------------
fs/gfs2/super.h | 3 +-
4 files changed, 373 insertions(+), 391 deletions(-)
--
2.20.1
next reply other threads:[~2019-03-17 17:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-17 17:40 Andrew Price [this message]
2019-03-17 17:40 ` [PATCH 1/2] gfs2: Convert gfs2 to fs_context Andrew Price
2019-03-17 17:40 ` [PATCH 2/2] gfs2: Convert gfs2meta " Andrew Price
2019-03-18 9:56 ` [Cluster-devel] [PATCH 0/2] gfs2: Switch to the new mount API Steven Whitehouse
2019-03-18 13:18 ` [PATCH 1/2] gfs2: Convert gfs2 to fs_context David Howells
2019-03-18 13:51 ` Andrew Price
2019-03-18 23:01 ` David Howells
2019-03-19 13:38 ` Andrew Price
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=20190317174027.15291-1-anprice@redhat.com \
--to=anprice@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@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).