From: Mike Frysinger <vapier@gentoo.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH v2] modpost: fix asprintf warnings
Date: Wed, 9 Dec 2009 20:16:19 -0500 [thread overview]
Message-ID: <1260407779-12517-1-git-send-email-vapier@gentoo.org> (raw)
In-Reply-To: <20091209155903.GB3247@hack>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1738 bytes --]
On compilers with security warnings enabled by default, we get:
scripts/mod/modpost.c: In function 'get_markers':
scripts/mod/modpost.c:1562: warning: ignoring return value of 'asprintf',
declared with attribute warn_unused_result
scripts/mod/modpost.c: In function 'add_marker':
scripts/mod/modpost.c:1982: warning: ignoring return value of 'asprintf',
declared with attribute warn_unused_result
So check the return value and abort on errors.
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
---
v2
- add missing newline pointed out by Américo Wang
scripts/mod/modpost.c | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/scripts/mod/modpost.c b/scripts/mod/modpost.c
index 801a16a..6608ebd 100644
--- a/scripts/mod/modpost.c
+++ b/scripts/mod/modpost.c
@@ -1559,7 +1559,8 @@ static void get_markers(struct elf_info *info, struct module *mod)
const char *name = strings + sym->st_value;
const char *fmt = strchr(name, '\0') + 1;
char *line = NULL;
- asprintf(&line, "%s\t%s\t%s\n", name, mod->name, fmt);
+ if (asprintf(&line, "%s\t%s\t%s\n", name, mod->name, fmt) == -1)
+ fatal("asprintf() with %s failed\n", name);
NOFAIL(line);
mod->markers[n++] = line;
}
@@ -1979,7 +1980,8 @@ static void write_dump(const char *fname)
static void add_marker(struct module *mod, const char *name, const char *fmt)
{
char *line = NULL;
- asprintf(&line, "%s\t%s\t%s\n", name, mod->name, fmt);
+ if (asprintf(&line, "%s\t%s\t%s\n", name, mod->name, fmt) == -1)
+ fatal("asprintf() with %s failed\n", name);
NOFAIL(line);
mod->markers = NOFAIL(realloc(mod->markers, ((mod->nmarkers + 1) *
--
1.6.5.5
next prev parent reply other threads:[~2009-12-10 1:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 12:02 [PATCH] " Mike Frysinger
2009-12-09 15:59 ` Américo Wang
2009-12-09 20:31 ` Mike Frysinger
2009-12-10 1:16 ` Mike Frysinger [this message]
2009-12-10 6:52 ` [PATCH v2] " Américo Wang
2009-12-10 11:07 ` Rusty Russell
2009-12-10 11:52 ` Rusty Russell
2009-12-10 11:55 ` Mike Frysinger
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=1260407779-12517-1-git-send-email-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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®