From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] Fix segv on "-r" option if unknown rpc service
Date: Fri, 23 Sep 2022 05:31:44 +0900 [thread overview]
Message-ID: <87sfkjcfrj.fsf@mail.parknet.co.jp> (raw)
In-Reply-To: <20220922120105.7a200fd2@hermes.local> (Stephen Hemminger's message of "Thu, 22 Sep 2022 12:01:05 -0700")
Stephen Hemminger <stephen@networkplumber.org> writes:
> On Sun, 18 Sep 2022 02:50:54 +0900
> OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> wrote:
>
>> + } else {
>> + const char fmt[] = "%s%u";
>> + char *buf = NULL;
>> + int len = snprintf(buf, 0, fmt, prog,
>> + rhead->rpcb_map.r_prog);
>> + len++;
>> + buf = malloc(len);
>> + snprintf(buf, len, fmt, prog, rhead->rpcb_map.r_prog);
>> + c->name = buf;
>> }
>
> Thanks for finding the bug but this could be improved.
> This seems like the hard way to do this.
> You are reinventing asprintf().
Right, if this project is assuming the extension is available.
> Would this work instead.
Thanks.
> diff --git a/misc/ss.c b/misc/ss.c
> index ff985cd8cae9..9d3d0bd84df3 100644
> --- a/misc/ss.c
> +++ b/misc/ss.c
> @@ -1596,6 +1596,10 @@ static void init_service_resolver(void)
> if (rpc) {
> strncat(prog, rpc->r_name, 128 - strlen(prog));
> c->name = strdup(prog);
> + } else if (asprintf(&c->name, "%s%u",
> + prog, rhead->rpcb_map.r_prog) < 0) {
> + fprintf(stderr, "ss: asprintf failed to allocate buffer\n");
> + abort();
> }
>
> c->next = rlist;
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
prev parent reply other threads:[~2022-09-22 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 17:50 [PATCH iproute2] Fix segv on "-r" option if unknown rpc service OGAWA Hirofumi
2022-09-22 19:01 ` Stephen Hemminger
2022-09-22 20:31 ` OGAWA Hirofumi [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=87sfkjcfrj.fsf@mail.parknet.co.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).