From: Ido Schimmel <idosch@nvidia.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
petrm@nvidia.com, jianbol@nvidia.com, roid@nvidia.com,
vladbu@nvidia.com, olteanv@gmail.com, simon.horman@corigine.com,
baowen.zheng@corigine.com, marcelo.leitner@gmail.com,
Ido Schimmel <idosch@nvidia.com>
Subject: [PATCH net-next 00/14] net/sched: Better error reporting for offload failures
Date: Thu, 7 Apr 2022 10:35:19 +0300 [thread overview]
Message-ID: <20220407073533.2422896-1-idosch@nvidia.com> (raw)
This patchset improves error reporting to user space when offload fails
during the flow action setup phase. That is, when failures occur in the
actions themselves, even before calling device drivers. Requested /
reported in [1].
This is done by passing extack to the offload_act_setup() callback and
making use of it in the various actions.
Patches #1-#2 change matchall and flower to log error messages to user
space in accordance with the verbose flag.
Patch #3 passes extack to the offload_act_setup() callback from the
various call sites, including matchall and flower.
Patches #4-#11 make use of extack in the various actions to report
offload failures.
Patch #12 adds an error message when the action does not support offload
at all.
Patches #13-#14 change matchall and flower to stop overwriting more
specific error messages.
[1] https://lore.kernel.org/netdev/20220317185249.5mff5u2x624pjewv@skbuf/
Ido Schimmel (14):
net/sched: matchall: Take verbose flag into account when logging error
messages
net/sched: flower: Take verbose flag into account when logging error
messages
net/sched: act_api: Add extack to offload_act_setup() callback
net/sched: act_gact: Add extack messages for offload failure
net/sched: act_mirred: Add extack message for offload failure
net/sched: act_mpls: Add extack messages for offload failure
net/sched: act_pedit: Add extack message for offload failure
net/sched: act_police: Add extack messages for offload failure
net/sched: act_skbedit: Add extack messages for offload failure
net/sched: act_tunnel_key: Add extack message for offload failure
net/sched: act_vlan: Add extack message for offload failure
net/sched: cls_api: Add extack message for unsupported action offload
net/sched: matchall: Avoid overwriting error messages
net/sched: flower: Avoid overwriting error messages
include/net/act_api.h | 3 ++-
include/net/pkt_cls.h | 6 ++++--
include/net/tc_act/tc_gact.h | 15 +++++++++++++++
include/net/tc_act/tc_skbedit.h | 12 ++++++++++++
net/sched/act_api.c | 4 ++--
net/sched/act_csum.c | 3 ++-
net/sched/act_ct.c | 3 ++-
net/sched/act_gact.c | 13 ++++++++++++-
net/sched/act_gate.c | 3 ++-
net/sched/act_mirred.c | 4 +++-
net/sched/act_mpls.c | 10 +++++++++-
net/sched/act_pedit.c | 4 +++-
net/sched/act_police.c | 20 ++++++++++++++++----
net/sched/act_sample.c | 3 ++-
net/sched/act_skbedit.c | 10 +++++++++-
net/sched/act_tunnel_key.c | 4 +++-
net/sched/act_vlan.c | 4 +++-
net/sched/cls_api.c | 22 ++++++++++++++--------
net/sched/cls_flower.c | 14 ++++++--------
net/sched/cls_matchall.c | 19 +++++++------------
20 files changed, 128 insertions(+), 48 deletions(-)
--
2.33.1
next reply other threads:[~2022-04-07 7:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 7:35 Ido Schimmel [this message]
2022-04-07 7:35 ` [PATCH net-next 01/14] net/sched: matchall: Take verbose flag into account when logging error messages Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 02/14] net/sched: flower: " Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 03/14] net/sched: act_api: Add extack to offload_act_setup() callback Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 04/14] net/sched: act_gact: Add extack messages for offload failure Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 05/14] net/sched: act_mirred: Add extack message " Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 06/14] net/sched: act_mpls: Add extack messages " Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 07/14] net/sched: act_pedit: Add extack message " Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 08/14] net/sched: act_police: Add extack messages " Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 09/14] net/sched: act_skbedit: " Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 10/14] net/sched: act_tunnel_key: Add extack message " Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 11/14] net/sched: act_vlan: " Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 12/14] net/sched: cls_api: Add extack message for unsupported action offload Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 13/14] net/sched: matchall: Avoid overwriting error messages Ido Schimmel
2022-04-07 7:35 ` [PATCH net-next 14/14] net/sched: flower: " Ido Schimmel
2022-04-07 21:15 ` [PATCH net-next 00/14] net/sched: Better error reporting for offload failures Jamal Hadi Salim
2022-04-08 12:50 ` patchwork-bot+netdevbpf
2022-04-08 18:51 ` Marcelo Ricardo Leitner
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=20220407073533.2422896-1-idosch@nvidia.com \
--to=idosch@nvidia.com \
--cc=baowen.zheng@corigine.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jianbol@nvidia.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=roid@nvidia.com \
--cc=simon.horman@corigine.com \
--cc=vladbu@nvidia.com \
--cc=xiyou.wangcong@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