* v4.4-rc3 ext4 memory leak
@ 2015-12-03 22:21 Bart Van Assche
2015-12-04 15:22 ` Theodore Ts'o
0 siblings, 1 reply; 3+ messages in thread
From: Bart Van Assche @ 2015-12-03 22:21 UTC (permalink / raw)
To: Theodore Ts'o, Andreas Dilger; +Cc: linux-ext4
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
Bart.
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: v4.4-rc3 ext4 memory leak
2015-12-03 22:21 v4.4-rc3 ext4 memory leak Bart Van Assche
@ 2015-12-04 15:22 ` Theodore Ts'o
2015-12-04 17:27 ` Bart Van Assche
0 siblings, 1 reply; 3+ messages in thread
From: Theodore Ts'o @ 2015-12-04 15:22 UTC (permalink / raw)
To: Bart Van Assche; +Cc: Andreas Dilger, linux-ext4
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: v4.4-rc3 ext4 memory leak
2015-12-04 15:22 ` Theodore Ts'o
@ 2015-12-04 17:27 ` Bart Van Assche
0 siblings, 0 replies; 3+ messages in thread
From: Bart Van Assche @ 2015-12-04 17:27 UTC (permalink / raw)
To: Theodore Ts'o; +Cc: Andreas Dilger, linux-ext4@vger.kernel.org
On 12/04/2015 07:22 AM, Theodore Ts'o wrote:
> 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?
Hello Ted,
So far I only ran xfstests against the 4.4-rc3 kernel so I do not know
whether this also occurred with previous kernel versions.
kmemleak scans periodically for memory leaks. kmemleak started reporting
these leaks after test generic/037 had started. So I think one of the
first 37 tests triggered this leak.
Bart.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-12-04 18:58 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-12-03 22:21 v4.4-rc3 ext4 memory leak Bart Van Assche
2015-12-04 15:22 ` Theodore Ts'o
2015-12-04 17:27 ` Bart Van Assche
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.