From: Catalin Marinas <catalin.marinas@arm.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Possible memory leak via tty_ldisc_try_get
Date: Fri, 12 Jun 2009 10:21:48 +0100 [thread overview]
Message-ID: <1244798508.26670.20.camel@pc1117.cambridge.arm.com> (raw)
Hi Alan,
I noticed you pushed some changes to drivers/char/tty_ldisc.c recently.
I now get about 12 kmemleak reports like below (on an ARM platform):
kmemleak: unreferenced object 0xdfaffd60 (size 32):
comm "init", pid 1, jiffies 4294937946
backtrace:
[<c007b8fc>] kmemleak_alloc+0x14c/0x260
[<c0079624>] kmem_cache_alloc+0x90/0x98
[<c0147428>] tty_ldisc_try_get+0x14/0xac
[<c01475a4>] tty_ldisc_get+0x18/0x40
[<c0147850>] tty_ldisc_reinit+0x28/0x5c
[<c01478ac>] tty_ldisc_release+0x28/0x3c
[<c0143450>] tty_release_dev+0x3cc/0x428
[<c01434b8>] tty_release+0xc/0x14
[<c007eb60>] __fput+0x104/0x1c4
[<c007bb48>] filp_close+0x70/0x7c
[<c007bbc8>] sys_close+0x74/0xa8
[<c0022dc0>] ret_fast_syscall+0x0/0x2c
[<ffffffff>] 0xffffffff
Could you please check whether the code is leaking memory? Let me know
if you need more information.
Thanks.
--
Catalin
next reply other threads:[~2009-06-12 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 9:21 Catalin Marinas [this message]
2009-06-12 10:22 ` Alan Cox
2009-06-25 13:29 ` 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=1244798508.26670.20.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®