From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Jesper Dangaard Brouer <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
Lorenzo Bianconi <lorenzo@kernel.org>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Stanislav Fomichev <sdf@google.com>,
Gerhard Engleder <gerhard@engleder-embedded.com>,
Simon Horman <horms@kernel.org>
Cc: Marek Majtyka <alardam@gmail.com>,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH net] veth: Update XDP feature set when bringing up device
Date: Tue, 12 Sep 2023 15:15:21 +0200 [thread overview]
Message-ID: <87zg1rjzx2.fsf@toke.dk> (raw)
In-Reply-To: <05c3dcacfd80076bcb09bb701eab88769818c80f.camel@redhat.com>
Paolo Abeni <pabeni@redhat.com> writes:
> On Tue, 2023-09-12 at 14:54 +0200, Toke Høiland-Jørgensen wrote:
>> Paolo Abeni <pabeni@redhat.com> writes:
>>
>> > Hi,
>> >
>> > On Mon, 2023-09-11 at 15:58 +0200, Toke Høiland-Jørgensen wrote:
>> > > There's an early return in veth_set_features() if the device is in a down
>> > > state, which leads to the XDP feature flags not being updated when enabling
>> > > GRO while the device is down. Which in turn leads to XDP_REDIRECT not
>> > > working, because the redirect code now checks the flags.
>> > >
>> > > Fix this by updating the feature flags after bringing the device up.
>> > >
>> > > Before this patch:
>> > >
>> > > NETDEV_XDP_ACT_BASIC: yes
>> > > NETDEV_XDP_ACT_REDIRECT: yes
>> > > NETDEV_XDP_ACT_NDO_XMIT: no
>> > > NETDEV_XDP_ACT_XSK_ZEROCOPY: no
>> > > NETDEV_XDP_ACT_HW_OFFLOAD: no
>> > > NETDEV_XDP_ACT_RX_SG: yes
>> > > NETDEV_XDP_ACT_NDO_XMIT_SG: no
>> > >
>> > > After this patch:
>> > >
>> > > NETDEV_XDP_ACT_BASIC: yes
>> > > NETDEV_XDP_ACT_REDIRECT: yes
>> > > NETDEV_XDP_ACT_NDO_XMIT: yes
>> > > NETDEV_XDP_ACT_XSK_ZEROCOPY: no
>> > > NETDEV_XDP_ACT_HW_OFFLOAD: no
>> > > NETDEV_XDP_ACT_RX_SG: yes
>> > > NETDEV_XDP_ACT_NDO_XMIT_SG: yes
>> > >
>> > > Fixes: fccca038f300 ("veth: take into account device reconfiguration for xdp_features flag")
>> > > Fixes: 66c0e13ad236 ("drivers: net: turn on XDP features")
>> > > Signed-off-by: Toke Høiland-Jørgensen <toke@redhat.com>
>> > > ---
>> > > drivers/net/veth.c | 2 ++
>> > > 1 file changed, 2 insertions(+)
>> > >
>> > > diff --git a/drivers/net/veth.c b/drivers/net/veth.c
>> > > index 9c6f4f83f22b..0deefd1573cf 100644
>> > > --- a/drivers/net/veth.c
>> > > +++ b/drivers/net/veth.c
>> > > @@ -1446,6 +1446,8 @@ static int veth_open(struct net_device *dev)
>> > > netif_carrier_on(peer);
>> > > }
>> > >
>> > > + veth_set_xdp_features(dev);
>> > > +
>> > > return 0;
>> > > }
>> >
>> > The patch LGTM, thanks!
>> >
>> > I think it would be nice to add some specific self-tests here. Could
>> > you please consider following-up with them?
>>
>> Sure! Do you want me to resubmit this as well, or are you just going to
>> apply it as-is and do the selftest as a follow-up?
>
> I think the latter is simpler and works for me. The self-test could
> target net-next, the fix is going to land there shortly after -net.
ACK, SGTM!
-Toke
next prev parent reply other threads:[~2023-09-12 13:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 13:58 [PATCH net] veth: Update XDP feature set when bringing up device Toke Høiland-Jørgensen
2023-09-12 10:07 ` Paolo Abeni
2023-09-12 12:54 ` Toke Høiland-Jørgensen
2023-09-12 13:10 ` Paolo Abeni
2023-09-12 13:15 ` Toke Høiland-Jørgensen [this message]
2023-09-12 14:40 ` 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=87zg1rjzx2.fsf@toke.dk \
--to=toke@redhat.com \
--cc=alardam@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gerhard@engleder-embedded.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=lorenzo@kernel.org \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.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