Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932369AbdDPXaj (ORCPT ); Sun, 16 Apr 2017 19:30:39 -0400 Received: from bh-25.webhostbox.net ([208.91.199.152]:53654 "EHLO bh-25.webhostbox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932279AbdDPXag (ORCPT ); Sun, 16 Apr 2017 19:30:36 -0400 Subject: Re: [PATCH 3.18 000/145] 3.18.49-stable review To: Greg Kroah-Hartman , linux-kernel@vger.kernel.org References: <20170416080200.205458595@linuxfoundation.org> Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org, shuahkh@osg.samsung.com, patches@kernelci.org, ben.hutchings@codethink.co.uk, stable@vger.kernel.org From: Guenter Roeck Message-ID: Date: Sun, 16 Apr 2017 16:30:32 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20170416080200.205458595@linuxfoundation.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated_sender: linux@roeck-us.net X-OutGoing-Spam-Status: No, score=-1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bh-25.webhostbox.net X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - roeck-us.net X-Get-Message-Sender-Via: bh-25.webhostbox.net: authenticated_id: linux@roeck-us.net X-Authenticated-Sender: bh-25.webhostbox.net: linux@roeck-us.net X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2246 Lines: 52 On 04/16/2017 03:48 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 3.18.49 release. > There are 145 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > --------- > Wait, what? 3.18? Wasn't that kernel dead and forgotten and left to > rot on the side of the road? Yes, it was, but unfortunately, there's a > few million or so devices out there in the wild that still rely on this > kernel. Now, some of their manufacturers and SoC vendors might not be > keeping their kernels up to date very well, but some do actually care > about security and their users, so this release is for them. If you > happen to have a vendor that does not care about their users, go > complain, as odds are, your device is very insecure right now... > > Because of this strange situation, and thanks to some vendors backing > the effort[1], I'll keep 3.18-stable alive in a semi-active mode, doing > releases every once in a while to keep it up to date and working well > based on what is happening in other more well-maintained stable kernels > (hint, use 4.4 or 4.9 or newer PLEASE, if your vendor refuses to do so, > switch vendors, it's the only way they will learn...) I don't know how > long I'll keep doing this, so if you care about 3.18, please contact me > to let me know the expected lifespan of your device. > > And finally, due to the delay from the last 3.18-stable kernel release, > there is a large backlog of patches, this is about 1/2 of the pending > ones so far. I'll be working on catching up to the rest of them over > the next few weeks, and then the updates should be smaller than this > one. > > ok, back to your normal form-letter stable -rc release notice: > --------- > > Responses should be made by Tue Apr 18 08:01:19 UTC 2017. > Anything received after that time might be too late. > Build results: total: 140 pass: 139 fail: 1 Failed builds: parisc:allmodconfig Qemu test results: total: 111 pass: 111 fail: 0 Fixing the build failure requires commit 6c8afa88adce ("Input: gscps2 - fix MODULE_DEVICE_TABLE invocation"). Details are available at http://kerneltests.org/builders. Guenter