From: James Cloos <cloos@jhcloos.com>
To: linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org
Cc: David Rientjes <rientjes@google.com>
Subject: Re: Likely mem leak in 3.7
Date: Sat, 01 Dec 2012 17:48:28 -0500 [thread overview]
Message-ID: <m38v9he6cq.fsf@carbon.jhcloos.org> (raw)
In-Reply-To: <m31ufrg3d4.fsf@carbon.jhcloos.org> (James Cloos's message of "Sat, 17 Nov 2012 19:29:18 -0500")
I've extensively tested 2844a48706e5 (tip at the time I compiled) for
the last few days and have been unable to reproduce.
This bug appears to be fixed.
Thanks.
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
prev parent reply other threads:[~2012-12-01 23:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 23:26 James Cloos
2012-11-16 19:17 ` David Rientjes
2012-11-18 0:29 ` James Cloos
2012-12-01 22:48 ` James Cloos [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=m38v9he6cq.fsf@carbon.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
/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®