linux-kernel - RE: [PATCH 3.12 00/64] 3.12.54-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:	Mon, 15 Feb 2016 16:10:34 +0000
From:	"Winkler, Tomas" <tomas.winkler@...el.com>
To:	Jiri Slaby <jslaby@...e.cz>, Shuah Khan <shuahkh@....samsung.com>,
	"stable@...r.kernel.org" <stable@...r.kernel.org>
CC:	"linux@...ck-us.net" <linux@...ck-us.net>,
	"shuah.kh@...sung.com" <shuah.kh@...sung.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 3.12 00/64] 3.12.54-stable review



> -----Original Message-----
> From: Jiri Slaby [mailto:jslaby@...e.cz]
> Sent: Monday, February 15, 2016 17:20
> To: Shuah Khan <shuahkh@....samsung.com>; stable@...r.kernel.org
> Cc: linux@...ck-us.net; shuah.kh@...sung.com; linux-kernel@...r.kernel.org;
> Winkler, Tomas <tomas.winkler@...el.com>
> Subject: Re: [PATCH 3.12 00/64] 3.12.54-stable review
> 
> On 02/11/2016, 08:26 PM, Shuah Khan wrote:
> > On 02/11/2016 06:59 AM, Jiri Slaby wrote:
> >> This is the start of the stable review cycle for the 3.12.54 release.
> >> There are 64 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 Mon Feb 15 14:54:53 CET 2016.
> >> Anything received after that time might be too late.
> >>
> >> The whole patch series can be found in one patch at:
> >> 	http://kernel.org/pub/linux/kernel/people/jirislaby/stable-review/patch-
> 3.12.54-rc1.xz
> >> and the diffstat can be found below.
> >>
> >
> > Compiled and booted on my test system. I did see
> > one additional error message:
> >
> > mei_me 0000:00:16.0: version message write failed
> >
> > Anything to be concerned about?
> 
> I hope not, given there are no relevant changes in mei in this release.
> Ccing MEI maintainer if this rings a bell?


On what platform is this happening? Do you have a more content in the log?
Thanks
Tomas