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>] [day] [month] [year] [list]
Date:   Sun, 26 Feb 2017 23:53:08 +0100
From:   Alexandre Belloni <alexandre.belloni@...e-electrons.com>
To:     Kevin Hilman <khilman@...libre.com>
Cc:     "kernelci.org bot" <bot@...nelci.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        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, stable@...r.kernel.org
Subject: Re: [PATCH 4.9 00/32] 4.9.13-stable review

On 26/02/2017 at 13:50:56 -0800, Kevin Hilman wrote:
> [ + Alexandre Belloni for the at91 issue ]
> 
> kernelci.org bot <bot@...nelci.org> writes:
> 
> > stable-rc boot: 211 boots: 1 failed, 201 passed with 9 offline (v4.9.12-33-g0417d46eeb59)
> >
> > Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/kernel/v4.9.12-33-g0417d46eeb59/
> > Full Build Summary: https://kernelci.org/build/stable-rc/kernel/v4.9.12-33-g0417d46eeb59/
> >
> > Tree: stable-rc
> > Branch: local/linux-4.9.y
> > Git Describe: v4.9.12-33-g0417d46eeb59
> > Git Commit: 0417d46eeb59b912a361bd35e1da2c2488f0d7c9
> > Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> > Tested: 54 unique boards, 17 SoC families, 27 builds out of 206
> >
> > Boot Failure Detected:
> >
> > arm:
> >
> >     multi_v7_defconfig+CONFIG_PROVE_LOCKING=y
> >         at91-sama5d2_xplained: 1 failed lab
> >
> 
> I'm guessing this is the same problem we've seen on other at91 platforms
> with UART overruns when CONFIG_PROVE_LOCKING is enabled.
> 
> If so, it's a known issue with a patch for mainline proposed, but not
> sure about the status of the stable backports.  Alexandre?
> 

It landed in Linus' tree on Friday and is properly marked for stable so
it is a matter of time until it is picked up by the stable maintainers.

-- 
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ