From: Greg KH <gregkh@linuxfoundation.org>
To: Ido Schimmel <idosch@nvidia.com>
Cc: stable@vger.kernel.org, kuba@kernel.org, vladbu@nvidia.com,
stable-commits@vger.kernel.org
Subject: Re: Patch "vlan: Fix VLAN 0 memory leak" has been added to the 6.4-stable tree
Date: Sun, 13 Aug 2023 18:20:21 +0200 [thread overview]
Message-ID: <2023081310-flame-pushup-a252@gregkh> (raw)
In-Reply-To: <ZNiK6AVGEZX6Y04c@shredder>
On Sun, Aug 13, 2023 at 10:48:56AM +0300, Ido Schimmel wrote:
> + stable
>
> On Sat, Aug 12, 2023 at 08:02:46PM +0200, gregkh@linuxfoundation.org wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > vlan: Fix VLAN 0 memory leak
> >
> > to the 6.4-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > vlan-fix-vlan-0-memory-leak.patch
> > and it can be found in the queue-6.4 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
> Please do not add the patch to the stable tree. A problem was found and
> a revert was posted:
> https://patchwork.kernel.org/project/netdevbpf/patch/20230811154523.1877590-1-vladbu@nvidia.com/
>
> In addition to 6.4, please do not apply to: 6.1, 5.15, 5.10, 5.4, 4.19,
> 4.14
Now dropped from everywhere, thanks.
greg k-h
prev parent reply other threads:[~2023-08-13 16:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2023081245-ebony-gladly-b428@gregkh>
2023-08-13 7:48 ` Patch "vlan: Fix VLAN 0 memory leak" has been added to the 6.4-stable tree Ido Schimmel
2023-08-13 16:20 ` Greg KH [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=2023081310-flame-pushup-a252@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=vladbu@nvidia.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).