From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755524AbbGUP1x (ORCPT ); Tue, 21 Jul 2015 11:27:53 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:33285 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754360AbbGUP1v (ORCPT ); Tue, 21 Jul 2015 11:27:51 -0400 Date: Tue, 21 Jul 2015 08:27:49 -0700 From: Greg KH To: Konstantin Khlebnikov Cc: linux-unionfs@vger.kernel.org, Miklos Szeredi , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH 1/2] ovl: free stack of paths in ovl_fill_super Message-ID: <20150721152749.GA2833@kroah.com> References: <20150721145843.11975.3849.stgit@buzz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150721145843.11975.3849.stgit@buzz> User-Agent: Mutt/1.5.23+102 (2ca89bed6448) (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 21, 2015 at 05:58:43PM +0300, Konstantin Khlebnikov wrote: > This fixes small memory leak after each successful mount. > Kmemleak report: > > unreferenced object 0xffff88003683fe00 (size 16): > comm "mount", pid 2029, jiffies 4294909563 (age 33.380s) > hex dump (first 16 bytes): > 20 27 1f bb 00 88 ff ff 40 4b 0f 36 02 88 ff ff '......@K.6.... > backtrace: > [] create_object+0x124/0x2c0 > [] kmemleak_alloc+0x7b/0xc0 > [] __kmalloc+0x106/0x340 > [] ovl_fill_super+0x389/0x9a0 [overlay] > [] mount_nodev+0x54/0xa0 > [] ovl_mount+0x18/0x20 [overlay] > [] mount_fs+0x43/0x170 > [] vfs_kern_mount+0x74/0x170 > [] do_mount+0x22d/0xdf0 > [] SyS_mount+0x7b/0xc0 > [] entry_SYSCALL_64_fastpath+0x12/0x76 > [] 0xffffffffffffffff > > Signed-off-by: Konstantin Khlebnikov > Fixes: a78d9f0d5d5c ("ovl: support multiple lower layers") > --- > fs/overlayfs/super.c | 1 + > 1 file changed, 1 insertion(+) This is not the correct way to submit patches for inclusion in the stable kernel tree. Please read Documentation/stable_kernel_rules.txt for how to do this properly.