From: Christoph Hellwig <hch@infradead.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org
Subject: Re: [2.6 patch] unexport get_fs_type
Date: Mon, 21 Apr 2008 04:54:28 -0400 [thread overview]
Message-ID: <20080421085428.GB17709@infradead.org> (raw)
In-Reply-To: <20080421084758.GK26897@cs181133002.pp.htv.fi>
On Mon, Apr 21, 2008 at 11:47:58AM +0300, Adrian Bunk wrote:
> This patch removes the no longer used export of get_fs_type.
Again, patch is good but missing an explanation. get_fs_type grabs a
reference to the file_system_type which needs to be dropped using
put_filesystem which is not exported, so it can't be used from modules
without introducing a bug. Nor should it because it's an operation
that's only useful during mount VFS-level code. The only really valid
user is fs/super.c
next prev parent reply other threads:[~2008-04-21 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 8:47 [2.6 patch] unexport get_fs_type Adrian Bunk
2008-04-21 8:54 ` Christoph Hellwig [this message]
2008-04-21 9:12 ` Al Viro
2008-04-21 9:07 ` 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=20080421085428.GB17709@infradead.org \
--to=hch@infradead.org \
--cc=bunk@kernel.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).