From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
To: "Linux Kernel, Mailing List" <linux-kernel@vger.kernel.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: [BUG] kmemleak on __radix_tree_preload
Date: Fri, 25 Apr 2014 10:45:40 +0900 [thread overview]
Message-ID: <1398390340.4283.36.camel@kjgkr> (raw)
Hi mm folks,
When I was testing recent linus tree, I got several kmemleaks as below.
Could any of you guys guide how to fix this?
Thanks,
0. Test
- fsstress on f2fs
1. Kernel version
commit 4d0fa8a0f01272d4de33704f20303dcecdb55df1
Merge: 39bfe90 b5539fa
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Tue Apr 22 09:28:02 2014 -0700
Merge tag 'gpio-v3.15-2' of
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio
Pull gpio fixes from Linus Walleij:
2. Bug
This is one of the results, but all the results indicate
__radix_tree_preload.
unreferenced object 0xffff88002ae2a238 (size 576):
comm "fsstress", pid 25019, jiffies 4295651360 (age 2276.104s)
hex dump (first 32 bytes):
01 00 00 00 81 ff ff ff 00 00 00 00 00 00 00 00 ................
40 7d 37 81 ff ff ff ff 50 a2 e2 2a 00 88 ff ff @}7.....P..*....
backtrace:
[<ffffffff8170e546>] kmemleak_alloc+0x26/0x50
[<ffffffff8119feac>] kmem_cache_alloc+0xdc/0x190
[<ffffffff81378709>] __radix_tree_preload+0x49/0xc0
[<ffffffff813787a1>] radix_tree_maybe_preload+0x21/0x30
[<ffffffff8114bbbc>] add_to_page_cache_lru+0x3c/0xc0
[<ffffffff8114c778>] grab_cache_page_write_begin+0x98/0xf0
[<ffffffffa02d3151>] f2fs_write_begin+0xa1/0x370 [f2fs]
[<ffffffff8114af47>] generic_perform_write+0xc7/0x1e0
[<ffffffff8114d230>] __generic_file_aio_write+0x1d0/0x400
[<ffffffff8114d4c0>] generic_file_aio_write+0x60/0xe0
[<ffffffff811b281a>] do_sync_write+0x5a/0x90
[<ffffffff811b3575>] vfs_write+0xc5/0x1f0
[<ffffffff811b3a92>] SyS_write+0x52/0xb0
[<ffffffff81730912>] system_call_fastpath+0x16/0x1b
[<ffffffffffffffff>] 0xffffffffffffffff
--
Jaegeuk Kim
Samsung
next reply other threads:[~2014-04-25 1:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 1:45 Jaegeuk Kim [this message]
2014-05-01 17:06 ` [BUG] kmemleak on __radix_tree_preload Catalin Marinas
2014-05-01 18:41 ` Johannes Weiner
2014-05-07 2:58 ` Jaegeuk Kim
2014-05-07 11:39 ` Catalin Marinas
2014-05-08 9:16 ` Jaegeuk Kim
2014-05-08 9:26 ` Catalin Marinas
2014-05-08 9:37 ` Jaegeuk Kim
2014-05-08 10:24 ` Catalin Marinas
2014-05-08 15:00 ` Paul E. McKenney
2014-05-08 15:29 ` Catalin Marinas
2014-05-08 15:53 ` Paul E. McKenney
2014-05-08 16:52 ` Catalin Marinas
2014-05-09 0:06 ` Jaegeuk Kim
2014-05-08 17:52 ` Johannes Weiner
2014-05-08 21:40 ` Catalin Marinas
2014-05-09 0:01 ` Jaegeuk Kim
2014-05-09 9:45 ` Catalin Marinas
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=1398390340.4283.36.camel@kjgkr \
--to=jaegeuk.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).