linux-kernel - Re: [PATCH 2.6.32 00/62] 2.6.32.68-longterm review

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <1442318791.29883.10.camel@decadent.org.uk>
Date:	Tue, 15 Sep 2015 13:06:31 +0100
From:	Ben Hutchings <ben@...adent.org.uk>
To:	Willy Tarreau <w@....eu>
Cc:	linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH 2.6.32 00/62] 2.6.32.68-longterm review

On Sun, 2015-09-13 at 00:56 +0200, Willy Tarreau wrote:
> This is the start of the longterm review cycle for the 2.6.32.68 release.
> All patches will be posted as a response to this one. If anyone has any
> issue with these being applied, please let me know. If anyone is a
> maintainer of the proper subsystem, and wants to add a Signed-off-by: line
> to the patch, please respond with it. If anyone thinks some important
> patches are missing and should be added prior to the release, please
> report them quickly with their respective mainline commit IDs.
> 
> Responses should be made by Sat Sep 19 00:56:05 CEST 2015.
> Anything received after that time might be too late. If someone
> wants a bit more time for a deeper review, please let me know.
> 
> NOTE: 2.6.32 is approaching end of support. There will probably be one
> or maybe two other versions issued in the next 3-6 months, and that will
> be all, at least for me. Adding to this the time it can take to validate
> and deploy in some environments, it probably makes sense to start to
> think about switching to another longterm branch. 3.2 and 3.4 are good
> candidates for those seeking rock-solid versions. Longterm branches and
> their projected EOLs are listed here :
> 
>      https://www.kernel.org/category/releases.html
> 
> The whole patch series can be found in one patch at :
>      https://kernel.org/pub/linux/kernel/v2.6/longterm-review/patch-2.6.32.68-rc1.gz
> 
> The shortlog and diffstat are appended below.
[...]

Patches 3 "crypto: testmgr - update LZO compression test vectors",
58 "dccp: fix auto-loading of dccp(_probe)",
60 "dccp: catch failed request_module call in dccp_probe init",
61 "dmaengine: fix missing cnt in ?: in dmatest" and
62 "ipv6: Fix return of xfrm6_tunnel_rcv()" have a git cherry-pick
line in the commit mesage rather than the usual "commit xxx upstream."

Patches 10 and 59 didn't reach me at all, though I can guess from its
neighbours that 59 is cherry-picked from commit
d984e6197ecd2babc1537f42dc1e676133005cda upstream.

Ben.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/