public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-kernel@vger.kernel.org, Namhyung Kim <namhyung@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>
Subject: Re: [RFC PATCH 0/8] perf tools: Update strbuf to remove xrealloc
Date: Sat, 30 Apr 2016 00:16:05 +0900	[thread overview]
Message-ID: <20160430001605.fc259a090aea64d337e75892@kernel.org> (raw)
In-Reply-To: <20160429145454.GK3386@kernel.org>

On Fri, 29 Apr 2016 11:54:54 -0300
Arnaldo Carvalho de Melo <acme@kernel.org> wrote:

> Em Fri, Apr 29, 2016 at 11:46:32PM +0900, Masami Hiramatsu escreveu:
> > Hi Arnaldo, 
> > 
> > This patch series does refactoring strbuf and xrealloc related code
> > to remove xrealloc since it can call die() to exit immediately when
> > it hits any error. Instead of that, it should return error code to
> > the caller so that the caller can handle its error.
> > 
> > Thus, at first, this changes the strbuf APIs to return error code
> > instead of die() immediately. And then changing API callers according
> > to the following rules.
> >  - Check the return value of strbuf APIs and handle errors and,
> >    - If the caller returns an error code (errno), it returns
> >      the return value of strbuf APIs.
> >    - If the caller just return -1 or NULl in error case, it also
> >      returns -1 or NULL in case of strbuf error. 
> >    - If the caller can call die() directly, it also call die()
> >      in case of strbuf error.
> >  - Error checking patches are splitted for each subcommand, since
> >    it will help review.
> > 
> > This also removes xrealloc and ALLOC_GROW from libperf, so that no
> > one use it anymore.
> > 
> > This series actually depends on the series of SDT support patches
> > which I've sent an hour ago. It is also able to change this not to
> > depend on it easily. Please ask me if you'd like so.
> 
> Please do so, as this one looks easier to review, so can go in faster.

OK, I sent it as v2 in order to avoid confusion.

Thank you!



-- 
Masami Hiramatsu <mhiramat@kernel.org>

      reply	other threads:[~2016-04-29 15:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-29 14:46 [RFC PATCH 0/8] perf tools: Update strbuf to remove xrealloc Masami Hiramatsu
2016-04-29 14:46 ` [RFC PATCH 1/8] perf: Rewrite strbuf not to die Masami Hiramatsu
2016-04-29 14:46 ` [RFC PATCH 2/8] perf probe: Check the return value of strbuf APIs Masami Hiramatsu
2016-04-29 14:47 ` [RFC PATCH 3/8] perf help: Make check_emacsclient_version to check " Masami Hiramatsu
2016-04-29 14:47 ` [RFC PATCH 4/8] perf: Make alias handler to check return value of strbuf Masami Hiramatsu
2016-04-29 14:47 ` [RFC PATCH 5/8] perf header: Make topology checkers " Masami Hiramatsu
2016-04-29 14:47 ` [RFC PATCH 6/8] perf pmu: Make pmu_formats_string " Masami Hiramatsu
2016-04-29 14:47 ` [RFC PATCH 7/8] perf help: Do not use ALLOC_GROW in add_cmd_list Masami Hiramatsu
2016-04-29 14:47 ` [RFC PATCH 8/8] perf tools: Remove xrealloc and ALLOC_GROW Masami Hiramatsu
2016-04-29 14:54 ` [RFC PATCH 0/8] perf tools: Update strbuf to remove xrealloc Arnaldo Carvalho de Melo
2016-04-29 15:16   ` Masami Hiramatsu [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=20160430001605.fc259a090aea64d337e75892@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=acme@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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