From: Chen Gang <gang.chen@asianux.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kernel: module: strncpy issue, using strlcpy instead of strncpy
Date: Tue, 09 Apr 2013 17:55:10 +0800 [thread overview]
Message-ID: <5163E57E.5030705@asianux.com> (raw)
In-Reply-To: <5163E123.5080205@asianux.com>
On 2013年04月09日 17:36, Chen Gang wrote:
> diff --git a/scripts/kallsyms.c b/scripts/kallsyms.c
> index 487ac6f..9ec6d1f 100644
> --- a/scripts/kallsyms.c
> +++ b/scripts/kallsyms.c
> @@ -145,13 +145,15 @@ static int read_symbol(FILE *in, struct sym_entry *s)
> /* include the type field in the symbol name, so that it gets
> * compressed together */
> s->len = strlen(str) + 1;
> + if (s->len > KSYM_NAME_LEN)
> + s->len = KSYM_NAME_LEN;
> s->sym = malloc(s->len + 1);
> if (!s->sym) {
> fprintf(stderr, "kallsyms failure: "
> "unable to allocate required amount of memory\n");
> exit(EXIT_FAILURE);
> }
> - strcpy((char *)s->sym + 1, str);
> + strlcpy((char *)s->sym + 1, str, KSYM_NAME_LEN);
> s->sym[0] = stype;
>
oh... it is a user mode program which no strlcpy in lib C !!
(so this diff is just really for a reference, not for the real using)
:-)
--
Chen Gang
Asianux Corporation
next prev parent reply other threads:[~2013-04-09 9:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-07 11:38 [PATCH] kernel: module: strncpy issue, using strlcpy instead of strncpy Chen Gang
2013-04-07 14:28 ` Geert Uytterhoeven
2013-04-08 2:48 ` Chen Gang
2013-04-08 3:02 ` Chen Gang
2013-04-08 5:30 ` Rusty Russell
2013-04-08 10:16 ` Chen Gang
2013-04-08 13:45 ` Rusty Russell
2013-04-09 1:52 ` Chen Gang
2013-04-09 9:36 ` Chen Gang
2013-04-09 9:55 ` Chen Gang [this message]
2013-04-10 6:00 ` Chen Gang
2013-04-09 2:47 ` [PATCH v2] kernel: module: using strlcpy and strcpy " Chen Gang
2013-04-10 1:22 ` Rusty Russell
2013-04-10 4:13 ` [PATCH v3] " Chen Gang
2013-04-10 6:52 ` Rusty Russell
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=5163E57E.5030705@asianux.com \
--to=gang.chen@asianux.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.