From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>,
netdev@vger.kernel.org, claudiu.manoil@nxp.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Subject: Re: [PATCH v3 net-next 0/2] enetc: unlock XDP_REDIRECT for XDP non-linear
Date: Tue, 13 Dec 2022 09:50:30 +0100 [thread overview]
Message-ID: <Y5g81tvyH6SJg26E@lore-desk> (raw)
In-Reply-To: <20221213003041.jgdotdqbodec2toz@skbuf>
[-- Attachment #1: Type: text/plain, Size: 1871 bytes --]
> On Mon, Dec 12, 2022 at 10:15:31PM +0100, Lorenzo Bianconi wrote:
> > Hi Vladimir,
> >
> > thx for testing. If we perform XDP_REDIRECT with SG XDP frames, the devmap
> > code will always return an error and the driver is responsible to free the
> > pending pages. Looking at the code, can the issue be the following?
> >
> > - enetc_flip_rx_buff() will unmap the page and set rx_swbd->page = NULL if
> > the page is not reusable.
> > - enetc_xdp_free() will not be able to free the page since rx_swbd->page is
> > NULL.
> >
> > What do you think? I am wondering if we have a similar issue for 'linear' XDP
> > buffer as well when xdp_do_redirect() returns an error. What do you think?
>
> A bit more complicated, but that's the gist, yes. Thanks for the hint.
> I was quite sure that this situation does not lead to a leak, because
> even though rx_swbd->page becomes NULL, the reference to it is not lost.
> But wrong I was. Not sure if you pointed out the condition where the
> page is not reusable because that's the only part that's problematic,
> or because you simply didn't notice that enetc_put_rx_buff() makes
> rx_swbd->page = NULL too. In any case, it's normally quite rare for a
> page to not be reusable, yet in this case, the way in which the page
> becomes non reusable is the key to the bug.
>
> Anyway, I've tested your patch set again with that fixed, and also
> submitted the fix here:
> https://patchwork.kernel.org/project/netdevbpf/patch/20221213001908.2347046-1-vladimir.oltean@nxp.com/
>
> It works as it should now. And yes, the issue should also be
> reproducible with single buffer XDP, if we redirect to a devmap which
> doesn't implement ndo_xdp_xmit or is down, for example.
ack, cool now it is fixed. I will repost the series when net-next is open
adding your tested-by.
Regards,
Lorenzo
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2022-12-13 8:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-10 13:53 [PATCH v3 net-next 0/2] enetc: unlock XDP_REDIRECT for XDP non-linear Lorenzo Bianconi
2022-12-10 13:53 ` [PATCH v3 net-next 1/2] net: ethernet: enetc: unlock XDP_REDIRECT for XDP non-linear buffers Lorenzo Bianconi
2022-12-10 13:53 ` [PATCH v3 net-next 2/2] net: ethernet: enetc: get rid of xdp_redirect_sg counter Lorenzo Bianconi
2022-12-12 19:51 ` [PATCH v3 net-next 0/2] enetc: unlock XDP_REDIRECT for XDP non-linear Vladimir Oltean
2022-12-12 21:15 ` Lorenzo Bianconi
2022-12-13 0:30 ` Vladimir Oltean
2022-12-13 8:50 ` Lorenzo Bianconi [this message]
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=Y5g81tvyH6SJg26E@lore-desk \
--to=lorenzo@kernel.org \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@nxp.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).