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:   Thu, 1 Jun 2017 19:32:35 +0200
From:   Paul Menzel <pmenzel@...gen.mpg.de>
To:     David Miller <davem@...emloft.net>
Cc:     Eric Dumazet <edumazet@...gle.com>, netdev@...r.kernel.org,
        ast@...nel.org, it+linux-netdev@...gen.mpg.de,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: Cherry pick commit *net: better skb->sender_cpu and skb->napi_id
 cohabitation* to 4.4 series?

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