All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Bart Van Assche <bart.vanassche@sandisk.com>
Cc: Andreas Dilger <adilger.kernel@dilger.ca>, linux-ext4@vger.kernel.org
Subject: Re: v4.4-rc3 ext4 memory leak
Date: Fri, 4 Dec 2015 10:22:32 -0500	[thread overview]
Message-ID: <20151204152232.GB3548@thunk.org> (raw)
In-Reply-To: <5660C06B.4010003@sandisk.com>

On Thu, Dec 03, 2015 at 02:21:31PM -0800, Bart Van Assche wrote:
> Hello,
> 
> Running xfstests on top of an ext4 filesystem causes kmemleak to report the
> following memory leak multiple times:
> 
> unreferenced object 0xffff880408709730 (size 96):
>   comm "fsstress", pid 35588, jiffies 4295006079 (age 11865.680s)
>   hex dump (first 32 bytes):
>     00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00  ................
>     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
>   backtrace:
>     [<ffffffff8151056a>] kmemleak_alloc+0x7a/0xc0
>     [<ffffffff81165e6e>] __kmalloc+0xde/0x140
>     [<ffffffffa022472e>] ext4_find_extent+0x26e/0x310 [ext4]
>     [<ffffffffa0227f15>] ext4_insert_range+0x255/0x3c0 [ext4]
>     [<ffffffffa022aca1>] ext4_fallocate+0x1f1/0x210 [ext4]
>     [<ffffffff81175fb6>] vfs_fallocate+0x156/0x1e0
>     [<ffffffff8117608e>] SyS_fallocate+0x4e/0x80
>     [<ffffffff8151b617>] entry_SYSCALL_64_fastpath+0x12/0x6f
>     [<ffffffffffffffff>] 0xffffffffffffffff

Is this something new?   i..e, was this reproducible on v4.3?

And can you isolate this to a specific test in xfstests?

Thanks,

						- Ted

  reply	other threads:[~2015-12-04 15:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-03 22:21 v4.4-rc3 ext4 memory leak Bart Van Assche
2015-12-04 15:22 ` Theodore Ts'o [this message]
2015-12-04 17:27   ` Bart Van Assche

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=20151204152232.GB3548@thunk.org \
    --to=tytso@mit.edu \
    --cc=adilger.kernel@dilger.ca \
    --cc=bart.vanassche@sandisk.com \
    --cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.