From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Taeung Song <treeze.taeung@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] tools/bpftool: Fix segfault case regarding 'pin' arguments
Date: Wed, 18 Jul 2018 11:19:49 -0700 [thread overview]
Message-ID: <20180718111949.325c985b@cakuba.lan> (raw)
In-Reply-To: <20180718133526.19669-2-treeze.taeung@gmail.com>
On Wed, 18 Jul 2018 22:35:26 +0900, Taeung Song wrote:
> Arguments of 'pin' subcommand should be checked
> at the very beginning of do_pin_any().
> Otherwise segfault errors can occur when using
> 'map pin' or 'prog pin' commands, so fix it.
>
> # bpftool prog pin id
> Segmentation fault
>
> Fixes: 71bb428fe2c1 ("tools: bpf: add bpftool")
> Cc: Jakub Kicinski <jakub.kicinski@netronome.com>
> Reported-by: Taehee Yoo <ap420073@gmail.com>
> Signed-off-by: Taeung Song <treeze.taeung@gmail.com>
> ---
> tools/bpf/bpftool/common.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/tools/bpf/bpftool/common.c b/tools/bpf/bpftool/common.c
> index 32f9e397a6c0..b1e1ba9e1c90 100644
> --- a/tools/bpf/bpftool/common.c
> +++ b/tools/bpf/bpftool/common.c
> @@ -217,6 +217,14 @@ int do_pin_any(int argc, char **argv, int (*get_fd_by_id)(__u32))
> int err;
> int fd;
>
> + if (argc < 3) {
> + p_err("too few arguments, id PROG_ID and FILE path is required");
Thanks for the fix! You can't say PROG_ID here, because this function
is also called by bpftool map pin id X. How about s/PROG_ID/ID/ ?
> + return -1;
> + } else if (argc > 3) {
> + p_err("too many arguments");
> + return -1;
> + }
> +
> if (!is_prefix(*argv, "id")) {
> p_err("expected 'id' got %s", *argv);
> return -1;
> @@ -230,9 +238,6 @@ int do_pin_any(int argc, char **argv, int (*get_fd_by_id)(__u32))
> }
> NEXT_ARG();
>
> - if (argc != 1)
> - usage();
> -
> fd = get_fd_by_id(id);
> if (fd < 0) {
> p_err("can't get prog by id (%u): %s", id, strerror(errno));
next prev parent reply other threads:[~2018-07-18 18:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 13:35 [PATCH 1/2] tools/bpftool: ignore build products Taeung Song
2018-07-18 13:35 ` [PATCH 2/2] tools/bpftool: Fix segfault case regarding 'pin' arguments Taeung Song
2018-07-18 18:19 ` Jakub Kicinski [this message]
2018-07-19 2:44 ` Taeung Song
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=20180718111949.325c985b@cakuba.lan \
--to=jakub.kicinski@netronome.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=treeze.taeung@gmail.com \
/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
Powered by JetHome