netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cong Wang <xiyou.wangcong@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
	Jiri Pirko <jiri@resnulli.us>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next] tc: Return an error if filters try to attach too many actions
Date: Wed, 9 Apr 2025 09:44:32 -0700	[thread overview]
Message-ID: <Z/aj8D1TRQBC7QtU@pop-os.localdomain> (raw)
In-Reply-To: <20250409145523.164506-1-toke@redhat.com>

On Wed, Apr 09, 2025 at 04:55:23PM +0200, Toke Høiland-Jørgensen wrote:
> While developing the fix for the buffer sizing issue in [0], I noticed
> that the kernel will happily accept a long list of actions for a filter,
> and then just silently truncate that list down to a maximum of 32
> actions.
> 
> That seems less than ideal, so this patch changes the action parsing to
> return an error message and refuse to create the filter in this case.
> This results in an error like:
> 
>  # ip link add type veth
>  # tc qdisc replace dev veth0 root handle 1: fq_codel
>  # tc -echo filter add dev veth0 parent 1: u32 match u32 0 0 $(for i in $(seq 33); do echo action pedit munge ip dport set 22; done)
> Error: Only 32 actions supported per filter.
> We have an error talking to the kernel
> 
> Instead of just creating a filter with 32 actions and dropping the last
> one.
> 
> This is obviously a change in UAPI. But seeing as creating more than 32
> filters has never actually *worked*, it seems that returning an explicit
> error is better, and any use cases that get broken by this were already
> broken just in more subtle ways.
> 
> [0] https://lore.kernel.org/r/20250407105542.16601-1-toke@redhat.com
> 
> Signed-off-by: Toke Høiland-Jørgensen <toke@redhat.com>
> ---
>  net/sched/act_api.c | 16 ++++++++++++++--
>  1 file changed, 14 insertions(+), 2 deletions(-)
> 
> diff --git a/net/sched/act_api.c b/net/sched/act_api.c
> index 839790043256..057e20cef375 100644
> --- a/net/sched/act_api.c
> +++ b/net/sched/act_api.c
> @@ -1461,17 +1461,29 @@ int tcf_action_init(struct net *net, struct tcf_proto *tp, struct nlattr *nla,
>  		    struct netlink_ext_ack *extack)
>  {
>  	struct tc_action_ops *ops[TCA_ACT_MAX_PRIO] = {};
> -	struct nlattr *tb[TCA_ACT_MAX_PRIO + 1];
> +	struct nlattr *tb[TCA_ACT_MAX_PRIO + 2];
>  	struct tc_action *act;
>  	size_t sz = 0;
>  	int err;
>  	int i;
>  
> -	err = nla_parse_nested_deprecated(tb, TCA_ACT_MAX_PRIO, nla, NULL,
> +	err = nla_parse_nested_deprecated(tb, TCA_ACT_MAX_PRIO + 1, nla, NULL,
>  					  extack);
>  	if (err < 0)
>  		return err;
>  
> +	/* The nested attributes are parsed as types, but they are really an
> +	 * array of actions. So we parse one more than we can handle, and return
> +	 * an error if the last one is set (as that indicates that the request
> +	 * contained more than the maximum number of actions).
> +	 */
> +	if (tb[TCA_ACT_MAX_PRIO + 1]) {
> +		NL_SET_ERR_MSG_FMT(extack,
> +				   "Only %d actions supported per filter",
> +				   TCA_ACT_MAX_PRIO);
> +		return -EINVAL;

I wonder ENOSPC is a better errno than EINVAL here?

Thanks.

  reply	other threads:[~2025-04-09 16:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-09 14:55 [PATCH net-next] tc: Return an error if filters try to attach too many actions Toke Høiland-Jørgensen
2025-04-09 16:44 ` Cong Wang [this message]
2025-04-10  0:10   ` Jakub Kicinski
2025-04-14 21:03     ` Cong Wang
2025-04-14 21:24       ` Jakub Kicinski
2025-04-15 14:46         ` Paolo Abeni
2025-04-16  0:20 ` patchwork-bot+netdevbpf

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=Z/aj8D1TRQBC7QtU@pop-os.localdomain \
    --to=xiyou.wangcong@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=toke@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 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).