From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Paolo Abeni <pabeni@redhat.com>, netdev@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
bpf@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] bpf: let bpf_warn_invalid_xdp_action() report more info
Date: Mon, 22 Nov 2021 12:32:29 +0100 [thread overview]
Message-ID: <87tug4cto2.fsf@toke.dk> (raw)
In-Reply-To: <2d7cdef73ce22021ee8ce40feeb9f084af066cea.1637339774.git.pabeni@redhat.com>
You still have:
> diff --git a/kernel/bpf/cpumap.c b/kernel/bpf/cpumap.c
> index 585b2b77ccc4..f7359bcb8fa3 100644
> --- a/kernel/bpf/cpumap.c
> +++ b/kernel/bpf/cpumap.c
> @@ -195,7 +195,7 @@ static void cpu_map_bpf_prog_run_skb(struct bpf_cpu_map_entry *rcpu,
> }
> return;
> default:
> - bpf_warn_invalid_xdp_action(act);
> + bpf_warn_invalid_xdp_action(skb->dev, rcpu->prog, act);
> fallthrough;
> case XDP_ABORTED:
> trace_xdp_exception(skb->dev, rcpu->prog, act);
> @@ -254,7 +254,7 @@ static int cpu_map_bpf_prog_run_xdp(struct bpf_cpu_map_entry *rcpu,
> }
> break;
> default:
> - bpf_warn_invalid_xdp_action(act);
> + bpf_warn_invalid_xdp_action(xdpf->dev_rx, rcpu->prog, act);
> fallthrough;
> case XDP_DROP:
> xdp_return_frame(xdpf);
> diff --git a/kernel/bpf/devmap.c b/kernel/bpf/devmap.c
> index f02d04540c0c..79bcf2169881 100644
> --- a/kernel/bpf/devmap.c
> +++ b/kernel/bpf/devmap.c
> @@ -348,7 +348,7 @@ static int dev_map_bpf_prog_run(struct bpf_prog *xdp_prog,
> frames[nframes++] = xdpf;
> break;
> default:
> - bpf_warn_invalid_xdp_action(act);
> + bpf_warn_invalid_xdp_action(dev, xdp_prog, act);
> fallthrough;
> case XDP_ABORTED:
> trace_xdp_exception(dev, xdp_prog, act);
> @@ -507,7 +507,7 @@ static u32 dev_map_bpf_prog_run_skb(struct sk_buff *skb, struct bpf_dtab_netdev
> __skb_push(skb, skb->mac_len);
> break;
> default:
> - bpf_warn_invalid_xdp_action(act);
> + bpf_warn_invalid_xdp_action(dst->dev, dst->xdp_prog, act);
> fallthrough;
> case XDP_ABORTED:
> trace_xdp_exception(dst->dev, dst->xdp_prog, act);
... and ...
> diff --git a/net/core/filter.c b/net/core/filter.c
> index 3ba584bb23f8..658f7a84d9bc 100644
> --- a/net/core/filter.c
> +++ b/net/core/filter.c
> @@ -8179,13 +8179,13 @@ static bool xdp_is_valid_access(int off, int size,
> return __is_valid_xdp_access(off, size);
> }
>
> -void bpf_warn_invalid_xdp_action(u32 act)
> +void bpf_warn_invalid_xdp_action(struct net_device *dev, struct bpf_prog *prog, u32 act)
> {
> const u32 act_max = XDP_REDIRECT;
>
> - pr_warn_once("%s XDP return value %u, expect packet loss!\n",
> + pr_warn_once("%s XDP return value %u on prog %s (id %d) dev %s, expect packet loss!\n",
> act > act_max ? "Illegal" : "Driver unsupported",
> - act);
> + act, prog->aux->name, prog->aux->id, dev->name);
> }
> EXPORT_SYMBOL_GPL(bpf_warn_invalid_xdp_action);
This will still print the dev name for cpumap and devmap programs, which
is misleading - it will have people looking at the drivers when the
problem is somewhere else.
I pointed this out multiple times in comments on your last revision so
I'm a bit puzzled as to why you're still doing this? :/
Just pass NULL as the dev from cpumap/devmap and don't print the dev
name in this case...
-Toke
next prev parent reply other threads:[~2021-11-22 11:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 16:39 [PATCH net-next 0/2] bpf: do not WARN in bpf_warn_invalid_xdp_action() Paolo Abeni
2021-11-19 16:39 ` [PATCH net-next 1/2] " Paolo Abeni
2021-11-19 16:39 ` [PATCH net-next 2/2] bpf: let bpf_warn_invalid_xdp_action() report more info Paolo Abeni
2021-11-22 11:32 ` Toke Høiland-Jørgensen [this message]
2021-11-24 9:13 ` Paolo Abeni
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=87tug4cto2.fsf@toke.dk \
--to=toke@redhat.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.