public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Dragos Tatulea <dtatulea@nvidia.com>
Cc: "jbrouer@redhat.com" <jbrouer@redhat.com>,
	"atzin@redhat.com" <atzin@redhat.com>,
	"linyunsheng@huawei.com" <linyunsheng@huawei.com>,
	"saeed@kernel.org" <saeed@kernel.org>,
	"ttoukan.linux@gmail.com" <ttoukan.linux@gmail.com>,
	"maxtram95@gmail.com" <maxtram95@gmail.com>,
	"kheib@redhat.com" <kheib@redhat.com>,
	"brouer@redhat.com" <brouer@redhat.com>,
	"jbenc@redhat.com" <jbenc@redhat.com>,
	"alexander.duyck@gmail.com" <alexander.duyck@gmail.com>,
	"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
	"ilias.apalodimas@linaro.org" <ilias.apalodimas@linaro.org>,
	Tariq Toukan <tariqt@nvidia.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"fmaurer@redhat.com" <fmaurer@redhat.com>,
	Saeed Mahameed <saeedm@nvidia.com>,
	"mkabat@redhat.com" <mkabat@redhat.com>,
	"lorenzo@kernel.org" <lorenzo@kernel.org>
Subject: Re: mlx5 XDP redirect leaking memory on kernel 6.3
Date: Mon, 17 Jul 2023 16:42:00 +0200	[thread overview]
Message-ID: <2023071705-senorita-unafraid-25b8@gregkh> (raw)
In-Reply-To: <32726772de5996305d0cfd4b6948933c47cb7927.camel@nvidia.com>

On Mon, Jul 17, 2023 at 02:37:44PM +0000, Dragos Tatulea wrote:
> On Thu, 2023-07-13 at 17:31 +0200, Greg KH wrote:
> > 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>
> So...I am a bit confused: should I send the patch to stable for 6.13 according
> to the stable submission rules or is it too late?

There is no "6.13" kernel version yet, that should not happen for
another year or so.

If you mean the "6.3.y" tree, yes, there is nothing to do here as that
tree is end-of-life and you should have moved to the 6.4.y kernel tree
at this point in time.

What is preventing you from moving?

thanks,

greg k-h

  reply	other threads:[~2023-07-17 14:42 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
2023-07-17 14:37           ` Dragos Tatulea
2023-07-17 14:42             ` gregkh [this message]
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=2023071705-senorita-unafraid-25b8@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