From: Catalin Marinas <catalin.marinas@arm.com>
To: Eric Paris <eparis@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Possible memory leak via inotify_add_watch
Date: Tue, 07 Jul 2009 14:03:53 +0100 [thread overview]
Message-ID: <1246971833.9451.39.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <1246932571.2866.90.camel@dhcp235-23.rdu.redhat.com>
On Mon, 2009-07-06 at 22:09 -0400, Eric Paris wrote:
> On Mon, 2009-07-06 at 23:03 +0100, Catalin Marinas wrote:
> > Hi Eric,
> >
> > I'm getting a few kmemleak reports like the one below (it may as well
> > be just a false positive). All of these allocations happened during
> > udevd.
>
> Any chance you could give this a shot and see if it fixes it up for you?
I'll give it a try tonight as it only shows on my home machine. But it
doesn't apply cleanly on 2.6.31-rc2, there is a big hunk in
inotify_update_watch() which fails to apply. Are there other additional
patches needed?
--
Catalin
next prev parent reply other threads:[~2009-07-07 13:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 22:03 Catalin Marinas
2009-07-06 22:59 ` Eric Paris
2009-07-07 2:09 ` Eric Paris
2009-07-07 13:03 ` Catalin Marinas [this message]
2009-07-07 13:11 ` Eric Paris
2009-07-07 16:24 ` Eric Paris
2009-07-07 21:30 ` 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=1246971833.9451.39.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=eparis@redhat.com \
--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®