linux-kernel - Re: [PATCH 3.18 00/39] 3.18.7-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: <20150209213736.GC11071@kroah.com>
Date:	Tue, 10 Feb 2015 05:37:36 +0800
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Shuah Khan <shuahkh@....samsung.com>
Cc:	linux-kernel@...r.kernel.org, alexander.usyskin@...el.com,
	tomas.winkler@...el.com, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, linux@...ck-us.net,
	satoru.takeuchi@...il.com, shuah.kh@...sung.com,
	stable@...r.kernel.org
Subject: Re: [PATCH 3.18 00/39] 3.18.7-stable review

On Mon, Feb 09, 2015 at 11:27:10AM -0700, Shuah Khan wrote:
> On 02/09/2015 01:33 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.18.7 release.
> > There are 39 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 Wed Feb 11 08:33:11 UTC 2015.
> > 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/v3.0/stable-review/patch-3.18.7-rc1.gz
> > and the diffstat can be found below.
> > 
> > thanks,
> > 
> > greg k-h
> > 
> 
> Compiled and booted on my test system.
> 
> I am seeing the following mei_me messages:
> 
> mei_me 0000:00:16.0: version message write failed: ret = -5
> mei_me 0000:00:16.0: hbm_start failed ret = -5
> mei_me 0000:00:16.0: version message write failed: ret = -5
> mei_me 0000:00:16.0: hbm_start failed ret = -5
> 
> Not concerned - maybe Alexander Usyskin and Tomas Winkler
> can take a look and see if this looks ok.
> 
> Could this be related to:
> 
> mei: clean reset bit before reset
> 
> commit b13a65ef190e488e2761d65bdd2e1fe8a3a125f5 upstream.

Odd, I wouldn't think that this commit would cause those errors to show
up, if so, that's not good.

Alexander, any thoughts?

thanks,

greg k-h
--
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/