From: Al Viro <viro@ZenIV.linux.org.uk>
To: Steven Liu <lingjiujianke@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
randy.dunlap@oracle.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, dchinner@redhat.com,
liuqi <liuqi@thunderst.com>
Subject: Re: [PATCH] code cleanup on fs/super.c
Date: Fri, 18 Feb 2011 03:08:47 +0000 [thread overview]
Message-ID: <20110218030846.GL22723@ZenIV.linux.org.uk> (raw)
In-Reply-To: <AANLkTinN1CamMpKZ5O3nDeV+LXpcMVZpxT59J7mJ5HQo@mail.gmail.com>
On Fri, Feb 18, 2011 at 10:45:12AM +0800, Steven Liu wrote:
> Hi AI Viro,
>
> I have saw this message, :)
>
> I think the nfs is using fs_type->get_sb, but it isn't using
> get_sb_bdev(or get_sb_nodev) .
> So if the nfs cannot let
> struct dentry *(*mount) (struct file_system_type *, int,
> const char *, void *);
> to replace
>
> int (*get_sb) (struct file_system_type *, int,
> const char *, void *, struct vfsmount *);
> Now, this patch cannot influence nfs normal use.
> Because get_sb is not must use get_sb_bdev or get_sb_nodev to get mnt,
> All the filesystem are using mount_bdev mount_nodev now, but it
> isn't called
> by get_sb,is called by *mount. Do you agreed with me?
Sigh... Yes, and it is irrelevant. There's simply no reason to remove
that stuff before the next merge window, when ->get_sb() is going to go
away _anyway_, along with those helpers. I am not saying that it can't
be done right now; there's simply no point in doing so. I don't particulary
care about hurting out-of-tree filesystems and if we had ->mnt_devname
series in this window I'd cheerfully ripped ->get_sb() out and let them
deal with it. However, I don't see any reasons for removing the helpers
in this cycle. What for? To force the (trivial) switch to ->mount() in
out-of-tree block filesystems one cycle earlier?
next prev parent reply other threads:[~2011-02-18 3:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 8:59 [PATCH] code cleanup on fs/super.c Steven Liu
2011-02-17 16:20 ` Linus Torvalds
2011-02-17 17:25 ` Ted Ts'o
2011-02-17 17:36 ` Al Viro
2011-02-18 2:45 ` Steven Liu
2011-02-18 3:08 ` Al Viro [this message]
2011-03-21 4:00 ` LiuQi
2011-03-21 4:43 ` Al Viro
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=20110218030846.GL22723@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=dchinner@redhat.com \
--cc=lingjiujianke@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuqi@thunderst.com \
--cc=randy.dunlap@oracle.com \
--cc=torvalds@linux-foundation.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).