From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Thomas Jarosch <thomas.jarosch@intra2net.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Re: [perf PATCH] Use pclose() instead of fclose() on pipe stream
Date: Wed, 16 Jan 2013 15:13:25 -0300 [thread overview]
Message-ID: <20130116181325.GL5826@ghostprotocols.net> (raw)
In-Reply-To: <1798138.DOH3quA1zP@storm>
Em Wed, Jan 16, 2013 at 10:09:48AM +0100, Thomas Jarosch escreveu:
>
> Alright, looks like I've messed up the "early" error path.
> The "FILE *fp" pointer needs to be initialized to NULL.
>
> Should I send another patch or do you want to fix it on the fly?
Please send another patch taking this into account.
> What about the other patch
> "[perf PATCH] Fix possible (unlikely) buffer overflow"
Its in my perf/core branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux
As soon as Ingo restarts processing pull requests I'll push it.
- Arnaldo
prev parent reply other threads:[~2013-01-16 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-25 16:02 [perf PATCH] Use pclose() instead of fclose() on pipe stream Thomas Jarosch
2013-01-11 4:16 ` Arnaldo Carvalho de Melo
2013-01-16 9:09 ` Thomas Jarosch
2013-01-16 18:13 ` Arnaldo Carvalho de Melo [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=20130116181325.GL5826@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.jarosch@intra2net.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;
as well as URLs for NNTP newsgroup(s).