From: Greg KH <gregkh@linuxfoundation.org>
To: Jesper Dangaard Brouer <jbrouer@redhat.com>
Cc: Dragos Tatulea <dtatulea@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>,
Saeed Mahameed <saeedm@nvidia.com>,
"saeed@kernel.org" <saeed@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
brouer@redhat.com, "maxtram95@gmail.com" <maxtram95@gmail.com>,
"lorenzo@kernel.org" <lorenzo@kernel.org>,
"alexander.duyck@gmail.com" <alexander.duyck@gmail.com>,
"kheib@redhat.com" <kheib@redhat.com>,
"ilias.apalodimas@linaro.org" <ilias.apalodimas@linaro.org>,
"mkabat@redhat.com" <mkabat@redhat.com>,
"atzin@redhat.com" <atzin@redhat.com>,
"fmaurer@redhat.com" <fmaurer@redhat.com>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
"jbenc@redhat.com" <jbenc@redhat.com>,
"linyunsheng@huawei.com" <linyunsheng@huawei.com>,
"ttoukan.linux@gmail.com" <ttoukan.linux@gmail.com>
Subject: Re: mlx5 XDP redirect leaking memory on kernel 6.3
Date: Thu, 13 Jul 2023 17:31:07 +0200 [thread overview]
Message-ID: <2023071357-unscrew-customary-fbae@gregkh> (raw)
In-Reply-To: <324a5a08-3053-6ab6-d47e-7413d9f2f443@redhat.com>
On Thu, Jul 13, 2023 at 04:58:04PM +0200, Jesper Dangaard Brouer wrote:
>
>
> On 13/07/2023 12.11, Dragos Tatulea wrote:
> > Gi Jesper,
> > On Thu, 2023-07-13 at 11:20 +0200, Jesper Dangaard Brouer wrote:
> > > Hi Dragos,
> > >
> > > Below you promised to work on a fix for XDP redirect memory leak...
> > > What is the status?
> > >
> > The fix got merged into net a week ago:
> > https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/ethernet/mellanox/mlx5/core?id=7abd955a58fb0fcd4e756fa2065c03ae488fcfa7
> >
> > Just forgot to follow up on this thread. Sorry about that...
> >
>
> Good to see it being fixed in net.git commit:
> 7abd955a58fb ("net/mlx5e: RX, Fix page_pool page fragment tracking for
> XDP")
>
> This need to be backported into stable tree 6.3, but I can see 6.3.13 is
> marked EOL (End-of-Life).
> Can we still get this fix applied? (Cc. GregKH)
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2023-07-13 15:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 15:55 mlx5 XDP redirect leaking memory on kernel 6.3 Jesper Dangaard Brouer
2023-05-23 16:35 ` Dragos Tatulea
2023-05-24 11:26 ` Yunsheng Lin
2023-05-24 11:29 ` Yunsheng Lin
2023-05-24 12:03 ` Dragos Tatulea
2023-05-24 12:43 ` Yunsheng Lin
2023-05-24 15:28 ` Jesper Dangaard Brouer
2023-07-13 9:20 ` Jesper Dangaard Brouer
2023-07-13 10:11 ` Dragos Tatulea
2023-07-13 14:58 ` Jesper Dangaard Brouer
2023-07-13 15:31 ` Greg KH [this message]
2023-07-17 14:37 ` Dragos Tatulea
2023-07-17 14:42 ` gregkh
2023-07-17 15:15 ` Dragos Tatulea
2023-07-28 13:14 ` Jesper Dangaard Brouer
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=2023071357-unscrew-customary-fbae@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alexander.duyck@gmail.com \
--cc=atzin@redhat.com \
--cc=bpf@vger.kernel.org \
--cc=brouer@redhat.com \
--cc=dtatulea@nvidia.com \
--cc=fmaurer@redhat.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jbenc@redhat.com \
--cc=jbrouer@redhat.com \
--cc=kheib@redhat.com \
--cc=linyunsheng@huawei.com \
--cc=lorenzo@kernel.org \
--cc=maxtram95@gmail.com \
--cc=mkabat@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=saeed@kernel.org \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=ttoukan.linux@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