From: Jeremy Allison <jra@samba.org>
To: Theodore Tso <tytso@mit.edu>
Cc: Jeremy Allison <jra@samba.org>, Jim Meyering <jim@meyering.net>,
samba-technical@lists.samba.org, linux-ext4@vger.kernel.org,
Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Subject: Re: avoid leak upon failed realloc
Date: Fri, 22 Jun 2007 14:02:12 -0700 [thread overview]
Message-ID: <20070622210212.GA11851@samba1> (raw)
In-Reply-To: <20070622202020.GJ15285@thunk.org>
On Fri, Jun 22, 2007 at 04:20:20PM -0400, Theodore Tso wrote:
>
> Hmm.... There are actually several realloc calls in the tdb sources,
> not just the one which Jim pointed out. If it's better I can just
> simply hack one of my patches to provide a realloc wrapper that deals
> with all of the cases in one fell swoop.
I checked. I think all other realloc uses in tdb are safe.
Jeremy.
prev parent reply other threads:[~2007-06-22 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-16 17:31 avoid leak upon failed realloc Jim Meyering
2007-06-18 14:04 ` Dave Kleikamp
2007-06-18 14:10 ` Jim Meyering
2007-06-22 6:41 ` Theodore Tso
2007-06-22 17:27 ` Jeremy Allison
2007-06-22 20:20 ` Theodore Tso
2007-06-22 21:02 ` Jeremy Allison [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=20070622210212.GA11851@samba1 \
--to=jra@samba.org \
--cc=jim@meyering.net \
--cc=linux-ext4@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=shaggy@linux.vnet.ibm.com \
--cc=tytso@mit.edu \
/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