Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Fri, 4 Oct 2019 13:20:23 -0400 (EDT)
From:   Bob Peterson <rpeterso@redhat.com>
To:     Andrew Price <anprice@redhat.com>
Cc:     cluster-devel@redhat.com,
        syzbot+c2fdfd2b783754878fb6@syzkaller.appspotmail.com,
        syzkaller-bugs@googlegroups.com, linux-kernel@vger.kernel.org
Message-ID: <824921067.4882112.1570209623167.JavaMail.zimbra@redhat.com>
In-Reply-To: <20191003153552.2015-1-anprice@redhat.com>
References: <000000000000afc1b40593f68888@google.com> <20191003153552.2015-1-anprice@redhat.com>
Subject: Re: [Cluster-devel] [PATCH] gfs2: Fix memory leak when gfs2meta's
        fs_context is freed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Thread-Topic: gfs2: Fix memory leak when gfs2meta's fs_context is freed
Thread-Index: Ei86TZNaiDR88EYSEPqE/xTVbulYpQ==
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

----- Original Message -----
> gfs2 and gfs2meta share an ->init_fs_context function which allocates an
> args structure stored in fc->fs_private. gfs2 registers a ->free
> function to free this memory when the fs_context is cleaned up, but
> there was not one registered for gfs2meta, causing a leak.
> 
> Register a ->free function for gfs2meta. The existing gfs2_fc_free
> function does what we need.
> 
> Reported-by: syzbot+c2fdfd2b783754878fb6@syzkaller.appspotmail.com
> Signed-off-by: Andrew Price <anprice@redhat.com>
> ---

Thanks. Now pushed to for-next.

Bob Peterson