linux-kernel - Re: [PATCH 4.3 000/200] 4.3.6-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]

Date:	Wed, 17 Feb 2016 12:39:47 -0800
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Shuah Khan <shuahkh@....samsung.com>
Cc:	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, linux@...ck-us.net,
	shuah.kh@...sung.com, patches@...nelci.org, stable@...r.kernel.org
Subject: Re: [PATCH 4.3 000/200] 4.3.6-stable review

On Mon, Feb 15, 2016 at 10:11:31AM -0700, Shuah Khan wrote:
> On 02/15/2016 08:16 AM, Shuah Khan wrote:
> > On 02/14/2016 03:20 PM, Greg Kroah-Hartman wrote:
> >> -------------------------
> >> NOTE: This is the last 4.3.y kernel to be released.  After this one, it
> >> is end-of-life, please move to 4.4.y at this point in time.
> >> -------------------------
> >>
> >> This is the start of the stable review cycle for the 4.3.6 release.
> >> There are 200 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 Tue Feb 16 22:21:48 UTC 2016.
> >> Anything received after that time might be too late.
> >>
> >> The whole patch series can be found in one patch at:
> >> 	kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.3.6-rc1.gz
> >> and the diffstat can be found below.
> >>
> > 
> > Compiled fine. I am seeing the following depmod warnings.
> > Something missing??
> > 
> 
> Didn't boot on my test system. Unfortunately
> I won't be able to debug this until Wednesday.

Were you able to determine what went wrong here?

thanks,

greg k-h