From: Catalin Marinas <catalin.marinas@arm.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Possible memory leak in fs/sysfs/bin.c
Date: Mon, 6 Jul 2009 23:30:41 +0100 [thread overview]
Message-ID: <b0943d9e0907061530u2d375fe5x91f92cfee3166c91@mail.gmail.com> (raw)
Hi,
I get about 28 (after 1 hour uptime) kmemleak reports like the one below:
unreferenced object 0xc24ab090 (size 4096):
comm "cat", pid 2930, jiffies 4294902918
backtrace:
[<c01e0c3a>] create_object+0xfa/0x250
[<c01e1e7d>] kmemleak_alloc+0x5d/0x70
[<c01dbc2d>] __kmalloc_track_caller+0x10d/0x1e0
[<c01bf5e4>] memdup_user+0x24/0x70
[<c02394d9>] write+0xb9/0x1b0
[<c01e480c>] vfs_write+0x9c/0x190
[<c01e49bd>] sys_write+0x3d/0x70
[<c010300c>] sysenter_do_call+0x12/0x38
[<ffffffff>] 0xffffffff
This is the write() function in the file mention in subject. It looks
to me like commit 1c8542c7bb replaced kmalloc() with memdup_user() but
also dropped the kfree(temp). The memdup_user() function allocates
memory but that's never freed in write().
Maybe something like this:
diff --git a/fs/sysfs/bin.c b/fs/sysfs/bin.c
index 9345806..bde6602 100644
--- a/fs/sysfs/bin.c
+++ b/fs/sysfs/bin.c
@@ -164,6 +164,7 @@ static ssize_t write(struct file *file, const char
__user *userbuf,
mutex_lock(&bb->mutex);
memcpy(bb->buffer, temp, count);
+ kfree(temp);
count = flush_write(dentry, bb->buffer, offs, count);
mutex_unlock(&bb->mutex);
--
Catalin
next reply other threads:[~2009-07-06 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 22:30 Catalin Marinas [this message]
2009-07-06 23:12 ` Parag Warudkar
2009-07-07 13:16 ` 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=b0943d9e0907061530u2d375fe5x91f92cfee3166c91@mail.gmail.com \
--to=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®