From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathon Reinhart <jonathon.reinhart@gmail.com>
Cc: stable@vger.kernel.org,
Linux Netdev List <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: Backport: "net: Make tcp_allowed_congestion_control readonly in non-init netns"
Date: Sun, 2 May 2021 13:09:09 +0200 [thread overview]
Message-ID: <YI6IVcl7I091C/jB@kroah.com> (raw)
In-Reply-To: <CAPFHKzdnmb=rXcAfKZYgAOz1M_5r=Cu6p1g+o0fi8VmncL1dbg@mail.gmail.com>
On Fri, Apr 30, 2021 at 11:45:51PM -0400, Jonathon Reinhart wrote:
> Hello,
>
> Please apply upstream git commit 2671fa4dc010 ("netfilter: conntrack:
> Make global sysctls readonly in non-init netns") to the stable trees.
>
> BTW netdev-FAQ.txt said not to send networking patches to stable, but
> Greg suggested I do it this way :-)
>
> On Mon, Apr 19, 2021 at 8:04 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> > For something like this, how about just waiting until it hits Linus's
> > tree and then email stable@vger.kernel.org saying, "please apply git
> > commit <SHA1> to the stable trees." and we can do so then.
>
> If there's a better way I should go about this, please let me know!
That's all that's needed, now queued up, thanks!
greg k-h
prev parent reply other threads:[~2021-05-02 11:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1618749928154136@kroah.com>
[not found] ` <CAPFHKzdKcVDDERr8pmd=65Tf=tWNh_bKar9OLQd0oS2YBVu80Q@mail.gmail.com>
[not found] ` <YH1xw5s0Uu5i/cRT@kroah.com>
2021-04-26 17:00 ` Patch "net: Make tcp_allowed_congestion_control readonly in non-init netns" has been added to the 5.10-stable tree Jonathon Reinhart
2021-05-01 3:45 ` Backport: "net: Make tcp_allowed_congestion_control readonly in non-init netns" Jonathon Reinhart
2021-05-02 11:09 ` 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=YI6IVcl7I091C/jB@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=jonathon.reinhart@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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).