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] [day] [month] [year] [list]
Message-ID: <5306BEBD.1040906@roeck-us.net>
Date:	Thu, 20 Feb 2014 18:49:33 -0800
From:	Guenter Roeck <linux@...ck-us.net>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, stable@...r.kernel.org
Subject: Re: [PATCH 3.13 00/40] 3.13.4-stable review

On 02/20/2014 03:32 PM, Greg Kroah-Hartman wrote:
> On Thu, Feb 20, 2014 at 03:23:32PM -0800, Guenter Roeck wrote:
>> On Thu, Feb 20, 2014 at 10:32:20AM -0800, Greg Kroah-Hartman wrote:
>>> On Tue, Feb 18, 2014 at 08:30:26PM -0800, Guenter Roeck wrote:
>>>> On Tue, Feb 18, 2014 at 02:47:01PM -0800, Greg Kroah-Hartman wrote:
>>>>> This is the start of the stable review cycle for the 3.13.4 release.
>>>>> There are 40 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 Thu Feb 20 22:44:22 UTC 2014.
>>>>> Anything received after that time might be too late.
>>>>>
>>>>
>>>> Build results:
>>>>      total: 126 pass: 122 skipped: 4 fail: 0
>>>>
>>>> qemu tests all passed.
>>>>
>>>> Details are available at http://server.roeck-us.net:8010/builders.
>>>>
>>>> Results are as expected.
>>>
>>> Thanks for testing and letting me know.  Interesting that the pstate
>>> buggy patch didn't hit your build system testing...
>>>
>> Nothing is perfect :-(. You mean the one where your builder
>> takes much more time to build the kernel with the patch applied,
>> or was here another one ?
>
> That same patch caused a bunch of boot-time failures on some systems.
> But not all of them, I think it depended on the hardware present.
>

My tests are not sophisticated enough to catch that kind of problem,
sorry. I am more surprised that Fenguang's test robot didn't find it;
that thing seems to catch pretty much everything nowadays.

Guenter


--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ