From: David Howells <dhowells@redhat.com>
To: Andrew Price <anprice@redhat.com>
Cc: dhowells@redhat.com, cluster-devel@redhat.com,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/2] gfs2: Convert gfs2 to fs_context
Date: Mon, 18 Mar 2019 13:18:19 +0000 [thread overview]
Message-ID: <28293.1552915099@warthog.procyon.org.uk> (raw)
In-Reply-To: <20190317174027.15291-2-anprice@redhat.com>
Andrew Price <anprice@redhat.com> wrote:
> sget() is still used instead of sget_fc() as there doesn't seem to be an
> obvious replacement for the bdev pointer propagation to the test/set
> functions (yet?)
Umm... What about the fs_context struct? Why can't that be used to propagate
the bdev pointer? That's kind of what it's for...
struct super_block *sget_fc(
struct fs_context *fc,
int (*test)(struct super_block *, struct fs_context *),
int (*set)(struct super_block *, struct fs_context *))
It looks like you should be able to stash the bdev pointer in the gfs2_args
struct.
> + fsparam_s32 ("commit", Opt_commit),
> + fsparam_s32 ("statfs_quantum", Opt_statfs_quantum),
> + fsparam_s32 ("statfs_percent", Opt_statfs_percent),
Why s32? Why not u32?
David
next prev parent reply other threads:[~2019-03-18 13:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-17 17:40 [PATCH 0/2] gfs2: Switch to the new mount API Andrew Price
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 ` David Howells [this message]
2019-03-18 13:51 ` [PATCH 1/2] gfs2: Convert gfs2 to fs_context 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=28293.1552915099@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=anprice@redhat.com \
--cc=cluster-devel@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).