From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
fuse-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: FUSE kmemleak report
Date: Tue, 6 Sep 2011 23:42:52 +0100 [thread overview]
Message-ID: <20110906224252.GA20218@sucs.org> (raw)
In-Reply-To: <874o0pkiao.fsf@tucsk.pomaz.szeredi.hu>
On Tue, Sep 06, 2011 at 01:43:27PM +0200, Miklos Szeredi wrote:
>
> Sitsofe, thanks for the report.
>
> Could you please try the patch below?
You're welcome. The patch resolves the leak for me on 3.1.0-rc5 on
Ubuntu 10.04 using GNOME 2.30.2 (I could previously reproduce it my
logging in as one user, logging out, logging in as another user and then
as root doing echo scan > /sys/kernel/debug/kmemleak ).
Tested-by: Sitsofe Wheeler <sitsofe@yahoo.com>
--
Sitsofe | http://sucs.org/~sits/
prev parent reply other threads:[~2011-09-06 22:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 22:37 FUSE kmemleak report Sitsofe Wheeler
2011-09-06 10:35 ` Catalin Marinas
2011-09-06 11:43 ` Miklos Szeredi
2011-09-06 22:42 ` Sitsofe Wheeler [this message]
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=20110906224252.GA20218@sucs.org \
--to=sitsofe@yahoo.com \
--cc=catalin.marinas@arm.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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).