netdev - Re: Cherry pick commit *net: better skb->sender_cpu and skb->napi

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 02 Jun 2017 14:37:19 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     xiyou.wangcong@...il.com
Cc:     pmenzel@...gen.mpg.de, edumazet@...gle.com, netdev@...r.kernel.org,
        ast@...nel.org, it+linux-netdev@...gen.mpg.de,
        gregkh@...uxfoundation.org
Subject: Re: Cherry pick commit *net: better skb->sender_cpu and
 skb->napi_id cohabitation* to 4.4 series?

From: Cong Wang <xiyou.wangcong@...il.com>
Date: Fri, 2 Jun 2017 10:51:39 -0700

> On Thu, Jun 1, 2017 at 10:32 AM, Paul Menzel <pmenzel@...gen.mpg.de> wrote:
>> 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?
> 
> +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.