[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ3xEMggVu7_9HUkNsTs2PHa25y-PeqPg6Kvvekavwrm6UzyKw@mail.gmail.com>
Date: Wed, 27 Feb 2019 00:42:06 +0200
From: Or Gerlitz <gerlitz.or@...il.com>
To: Tonghao Zhang <xiangxia.m.yue@...il.com>
Cc: Saeed Mahameed <saeedm@...lanox.com>,
Linux Netdev List <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next v2 5/5] net/mlx5e: Return -EOPNOTSUPP when
attempting to offload an unsupported action
On Mon, Feb 25, 2019 at 1:07 PM <xiangxia.m.yue@...il.com> wrote:
> The encapsulation is not supported for mlx5 VFs. When we try to
> offload that action, the -EINVAL is returned, but not -EOPNOTSUPP.
> This patch changes the returned value and ignore to confuse user.
FWIW, note that this changes the behavior towards user-space, I don't see
concrete harm done here but we should realize that
> For example: (p2p1_0 is VF net device)
> tc filter add dev p2p1_0 protocol ip parent ffff: prio 1 flower skip_sw \
> src_mac e4:11:22:33:44:01 \
> action tunnel_key set \
> src_ip 1.1.1.100 \
> dst_ip 1.1.1.200 \
> dst_port 4789 id 100 \
> action mirred egress redirect dev vxlan0
>
> "RTNETLINK answers: Invalid argument"
Powered by blists - more mailing lists