From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [PATCH] gfs2: fix file_system_type leak on gfs2meta mount
Date: Tue, 26 Feb 2008 03:27:48 +0000 [thread overview]
Message-ID: <1203996468.3291.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20080225175836.GA27910@lst.de>
Hi,
Now in the -nmw git tree. Thanks,
Steve.
On Mon, 2008-02-25 at 18:58 +0100, Christoph Hellwig wrote:
> get_gfs2_sb does a get_fs_type without doing a put_filesystem and
> thus leaking a file_system_type reference everytime it's called.
>
> Just use gfs2_fs_type directly instead of doing the lookup and thus
> fix the problem.
>
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> Index: linux-2.6/fs/gfs2/ops_fstype.c
> ===================================================================
> --- linux-2.6.orig/fs/gfs2/ops_fstype.c 2008-02-25 18:53:11.000000000 +0100
> +++ linux-2.6/fs/gfs2/ops_fstype.c 2008-02-25 18:53:36.000000000 +0100
> @@ -874,7 +874,6 @@ static struct super_block* get_gfs2_sb(c
> {
> struct kstat stat;
> struct nameidata nd;
> - struct file_system_type *fstype;
> struct super_block *sb = NULL, *s;
> int error;
>
> @@ -886,8 +885,7 @@ static struct super_block* get_gfs2_sb(c
> }
> error = vfs_getattr(nd.path.mnt, nd.path.dentry, &stat);
>
> - fstype = get_fs_type("gfs2");
> - list_for_each_entry(s, &fstype->fs_supers, s_instances) {
> + list_for_each_entry(s, &gfs2_fs_type.fs_supers, s_instances) {
> if ((S_ISBLK(stat.mode) && s->s_dev == stat.rdev) ||
> (S_ISDIR(stat.mode) &&
> s == nd.path.dentry->d_inode->i_sb)) {
prev parent reply other threads:[~2008-02-26 3:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 17:58 [Cluster-devel] [PATCH] gfs2: fix file_system_type leak on gfs2meta mount Christoph Hellwig
2008-02-26 3:27 ` Steven Whitehouse [this message]
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=1203996468.3291.6.camel@localhost.localdomain \
--to=swhiteho@redhat.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;
as well as URLs for NNTP newsgroup(s).