From: Julia Lawall <julia.lawall@lip6.fr>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v2] perf tools: Add error handling
Date: Tue, 09 Jun 2015 08:35:38 +0000 [thread overview]
Message-ID: <alpine.DEB.2.10.1506091032390.2324@hadrien> (raw)
In-Reply-To: <1433836196-20647-1-git-send-email-firogm@gmail.com>
On Tue, 9 Jun 2015, Firo Yang wrote:
> On Tue, Jun 09, 2015 at 10:05:24AM +0200, Julia Lawall wrote:
> >On Tue, 9 Jun 2015, Firo Yang wrote:
> >
> >> Add error handling code for snprintf and rename in check_backup.
> >>
> >> Signed-off-by: Firo Yang <firogm@gmail.com>
> >> ---
> >> Since there is no suitable error code snprintf, I just return the
> >> value returned by snprintf.
> >>
> >> tools/perf/util/data.c | 17 ++++++++++++++---
> >> 1 file changed, 14 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/tools/perf/util/data.c b/tools/perf/util/data.c
> >> index 1921942..26ab45a 100644
> >> --- a/tools/perf/util/data.c
> >> +++ b/tools/perf/util/data.c
> >> @@ -32,15 +32,26 @@ static bool check_pipe(struct perf_data_file *file)
> >>
> >> static int check_backup(struct perf_data_file *file)
> >> {
> >> + int ret;
> >> struct stat st;
> >>
> >> if (!stat(file->path, &st) && st.st_size) {
> >> - /* TODO check errors properly */
> >> char oldname[PATH_MAX];
> >> - snprintf(oldname, sizeof(oldname), "%s.old",
> >> + ret = snprintf(oldname, sizeof(oldname), "%s.old",
> >> file->path);
> >> + if (ret < 0) {
> >
> >Can it ever return a negative value anyway? It seems clear that it can
> I misunderstand the content in man 3 snprintf:
> If an output error is encountered, a negative value is returned.
It does say that, but I didn't see it in the code. Snprintf just returns
the value of vsnprintf. This can return 0 or str-buf. If str-buf can be
negative, the value would not seem to be very meaningful. But probably it
cannot be.
>
> It should be nothing related to snprintf.
>
> >return a positive value. That value might not be an appropriate result
> >for this function.
Sorry, this latter comment was nonsense :)
julia
> >julia
> >
> >> + pr_err("failed to make name %s.old\n", file->path);
> >> + return ret;
> >> + }
> >> +
> >> unlink(oldname);
> >> - rename(file->path, oldname);
> >> +
> >> + ret = rename(file->path, oldname);
> >> + if (ret < 0) {
> >> + pr_err("failed to rename %s to %s\n", file->path,
> >> + oldname);
> >> + return -errno;
> >
> >What is
> If rename failed, it would set the errno to the corresponding error
> number. You can find it in other function in the same file.
> >
> >> + }
> >> }
> >>
> >> return 0;
> >> --
> >> 2.4.2
> >>
> >> --
> >> To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
> >> the body of a message to majordomo@vger.kernel.org
> >> More majordomo info at http://vger.kernel.org/majordomo-info.html
> >>
>
> --
> --
> To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2015-06-09 8:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 7:49 [PATCH v2] perf tools: Add error handling Firo Yang
2015-06-09 8:05 ` Julia Lawall
2015-06-09 8:25 ` Firo Yang
2015-06-09 8:35 ` Julia Lawall [this message]
2015-06-09 8:54 ` Firo Yang
2015-06-09 12:37 ` walter harms
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=alpine.DEB.2.10.1506091032390.2324@hadrien \
--to=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.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