6 messages, 3 authors, 2017-06-02 · open the first message on its own page
From: Paul Menzel <hidden>
Date: 2017-06-01 12:43:32
Dear David, dear Eric, We noticed, that we manually apply commit 52bd2d62ce67 (net: better skb->sender_cpu and skb->napi_id cohabitation), present since v4.5-rc1, to our Linux 4.4 images. Would it be useful to have it included in the 4.4 series? Kind regards, Paul
From: David Miller <davem@davemloft.net>
Date: 2017-06-01 16:19:47
Neither of us have anything to do with the 4.4 -stable series. We only manage stable backport submissions for the most recent two releases.
From: Paul Menzel <hidden>
Date: 2017-06-01 17:32:38
Dear David, On 06/01/17 18:19, David Miller wrote:
Neither of us have anything to do with the 4.4 -stable series. We only manage stable backport submissions for the most recent two releases.
Thank you for the prompt response. Should the netdev FAQ be updated then to contain that information?
Q: How can I tell what patches are queued up for backporting to the
various stable releases?
A: Normally Greg Kroah-Hartman collects stable commits himself, but
for networking, Dave collects up patches he deems critical for the
networking subsystem, and then hands them off to Greg.
There is a patchworks queue that you can see here:
http://patchwork.ozlabs.org/bundle/davem/stable/?state=*
It contains the patches which Dave has selected, but not yet handed
off to Greg. If Greg already has the patch, then it will be here:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git
A quick way to find whether the patch is in this stable-queue is
to simply clone the repo, and then git grep the mainline commit ID, e.g.
stable-queue$ git grep -l 284041ef21fdf2e
releases/3.0.84/ipv6-fix-possible-crashes-in-ip6_cork_release.patch
releases/3.4.51/ipv6-fix-possible-crashes-in-ip6_cork_release.patch
releases/3.9.8/ipv6-fix-possible-crashes-in-ip6_cork_release.patch
stable/stable-queue$Kind regards, Paul [1] Documentation/networking/netdev-FAQ.txt
From: Cong Wang <hidden>
Date: 2017-06-02 17:52:01
On Thu, Jun 1, 2017 at 10:32 AM, Paul Menzel [off-list ref] wrote:
Dear David, On 06/01/17 18:19, David Miller wrote:quoted
Neither of us have anything to do with the 4.4 -stable series. We only manage stable backport submissions for the most recent two releases.Thank you for the prompt response. Should the netdev FAQ be updated then to contain that information?
+1 It is quite helpful to know which stable releases contain network fixes which don't, especially for those who rely on stable releases, at least we could do backport by ourselves when we know they are missing.
From: David Miller <davem@davemloft.net>
Date: 2017-06-02 18:37:21
From: Cong Wang <redacted> Date: Fri, 2 Jun 2017 10:51:39 -0700
On Thu, Jun 1, 2017 at 10:32 AM, Paul Menzel [off-list ref] wrote:quoted
Dear David, On 06/01/17 18:19, David Miller wrote:quoted
Neither of us have anything to do with the 4.4 -stable series. We only manage stable backport submissions for the most recent two releases.Thank you for the prompt response. Should the netdev FAQ be updated then to contain that information?+1 It is quite helpful to know which stable releases contain network fixes which don't, especially for those who rely on stable releases, at least we could do backport by ourselves when we know they are missing.
The people who maintain the -stable releases older than the ones Greg KH are doing typically scan the ones that Greg applies and tries to integrate them into their -stable releases when appropriate. If someone wants to write an accurate description of that and how it works, and add it to the FAQ, sure.
From: Paul Menzel <hidden>
Date: 2017-06-02 21:37:16
Dear David, On 2017-06-02 20:37, David Miller wrote:
From: Cong Wang <redacted> Date: Fri, 2 Jun 2017 10:51:39 -0700quoted
On Thu, Jun 1, 2017 at 10:32 AM, Paul Menzel [off-list ref] wrote:
quoted
quoted
On 06/01/17 18:19, David Miller wrote:quoted
Neither of us have anything to do with the 4.4 -stable series. We only manage stable backport submissions for the most recent two releases.Thank you for the prompt response. Should the netdev FAQ be updated then to contain that information?+1 It is quite helpful to know which stable releases contain network fixes which don't, especially for those who rely on stable releases, at least we could do backport by ourselves when we know they are missing.The people who maintain the -stable releases older than the ones Greg KH are doing typically scan the ones that Greg applies and tries to integrate them into their -stable releases when appropriate.
My understanding is, that Greg maintains the 4.4 (LTS) and 4.9 (LTS) series.
If someone wants to write an accurate description of that and how it works, and add it to the FAQ, sure.
I can do that, when I understand the policy. Kind regards, Paul