linux-kernel - Re: [PATCH 3.18 00/93] 3.18.103-stable 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: <20180407061006.GC18744@kroah.com>
Date:   Sat, 7 Apr 2018 08:10:06 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Harsh Shandilya <msfjarvis@...il.com>
Cc:     linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
        akpm@...ux-foundation.org, linux@...ck-us.net,
        shuahkh@....samsung.com, patches@...nelci.org,
        ben.hutchings@...ethink.co.uk, lkft-triage@...ts.linaro.org,
        stable@...r.kernel.org
Subject: Re: [PATCH 3.18 00/93] 3.18.103-stable review

On Sat, Apr 07, 2018 at 12:41:38AM +0530, Harsh Shandilya wrote:
> 
> 
> On 6 April 2018 6:52:29 PM IST, Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:
> >This is the start of the stable review cycle for the 3.18.103 release.
> >There are 93 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.
> >
> >Responses should be made by Sun Apr  8 08:42:04 UTC 2018.
> >Anything received after that time might be too late.
> >
> >The whole patch series can be found in one patch at:
> >	https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.103-rc1.gz
> >or in the git tree and branch at:
> >	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> >linux-3.18.y
> >and the diffstat can be found below.
> >
> >thanks,
> >
> >greg k-h
> 
> Builds and boots on the OnePlus3T, no visible regressions. The merge was slightly gnarly with "proc: revert /proc/<pid>/maps [stack:TID] annotation" conflicting due to kernel-common changes and the v4l2 series conflicting with CAF changes in the msm-3.18 tree.

Yeah, the merge is going to be a bit messy, not as messy as 4.9.y is
going to be :)

Thanks for testing and letting me know.

greg k-h