public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
Cc: linux-unionfs@vger.kernel.org, Miklos Szeredi <miklos@szeredi.hu>,
	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
Date: Tue, 21 Jul 2015 08:27:49 -0700	[thread overview]
Message-ID: <20150721152749.GA2833@kroah.com> (raw)
In-Reply-To: <20150721145843.11975.3849.stgit@buzz>

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:
>     [<ffffffff811f8cd4>] create_object+0x124/0x2c0
>     [<ffffffff817a059b>] kmemleak_alloc+0x7b/0xc0
>     [<ffffffff811dffe6>] __kmalloc+0x106/0x340
>     [<ffffffffa01b7a29>] ovl_fill_super+0x389/0x9a0 [overlay]
>     [<ffffffff81200ac4>] mount_nodev+0x54/0xa0
>     [<ffffffffa01b7118>] ovl_mount+0x18/0x20 [overlay]
>     [<ffffffff81201ab3>] mount_fs+0x43/0x170
>     [<ffffffff81220d34>] vfs_kern_mount+0x74/0x170
>     [<ffffffff812233ad>] do_mount+0x22d/0xdf0
>     [<ffffffff812242cb>] SyS_mount+0x7b/0xc0
>     [<ffffffff817b6bee>] entry_SYSCALL_64_fastpath+0x12/0x76
>     [<ffffffffffffffff>] 0xffffffffffffffff
> 
> Signed-off-by: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
> Fixes: a78d9f0d5d5c ("ovl: support multiple lower layers")
> ---
>  fs/overlayfs/super.c |    1 +
>  1 file changed, 1 insertion(+)

<formletter>

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.

</formletter>

      parent reply	other threads:[~2015-07-21 15:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-21 14:58 [PATCH 1/2] ovl: free stack of paths in ovl_fill_super Konstantin Khlebnikov
2015-07-21 14:58 ` [PATCH 2/2] ovl: free lower_mnt array in ovl_put_super Konstantin Khlebnikov
2015-07-21 15:27   ` Greg KH
2015-07-21 15:27 ` Greg KH [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=20150721152749.GA2833@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=khlebnikov@yandex-team.ru \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=stable@vger.kernel.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