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 14/14] net/sched: flower: Avoid overwriting error messages
Date: Thu, 7 Apr 2022 10:35:33 +0300 [thread overview]
Message-ID: <20220407073533.2422896-15-idosch@nvidia.com> (raw)
In-Reply-To: <20220407073533.2422896-1-idosch@nvidia.com>
The various error paths of tc_setup_offload_action() now report specific
error messages. Remove the generic messages to avoid overwriting the
more specific ones.
Before:
# tc filter add dev dummy0 ingress pref 1 proto ip flower skip_sw dst_ip 198.51.100.1 action police rate 100Mbit burst 10000
Error: cls_flower: Failed to setup flow action.
We have an error talking to the kernel
After:
# tc filter add dev dummy0 ingress pref 1 proto ip flower skip_sw dst_ip 198.51.100.1 action police rate 100Mbit burst 10000
Error: act_police: Offload not supported when conform/exceed action is "reclassify".
We have an error talking to the kernel
Signed-off-by: Ido Schimmel <idosch@nvidia.com>
Reviewed-by: Petr Machata <petrm@nvidia.com>
---
net/sched/cls_flower.c | 4 ----
1 file changed, 4 deletions(-)
diff --git a/net/sched/cls_flower.c b/net/sched/cls_flower.c
index acf827b0e30a..87e030dfc328 100644
--- a/net/sched/cls_flower.c
+++ b/net/sched/cls_flower.c
@@ -468,8 +468,6 @@ static int fl_hw_replace_filter(struct tcf_proto *tp,
cls_flower.common.extack);
if (err) {
kfree(cls_flower.rule);
- NL_SET_ERR_MSG_MOD(cls_flower.common.extack,
- "Failed to setup flow action");
return skip_sw ? err : 0;
}
@@ -2358,8 +2356,6 @@ static int fl_reoffload(struct tcf_proto *tp, bool add, flow_setup_cb_t *cb,
cls_flower.common.extack);
if (err) {
kfree(cls_flower.rule);
- NL_SET_ERR_MSG_MOD(cls_flower.common.extack,
- "Failed to setup flow action");
if (tc_skip_sw(f->flags)) {
__fl_put(f);
return err;
--
2.33.1
next prev parent reply other threads:[~2022-04-07 7:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 7:35 [PATCH net-next 00/14] net/sched: Better error reporting for offload failures Ido Schimmel
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 ` Ido Schimmel [this message]
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-15-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