linux-kernel - Re: [PATCH 4.9 00/66] 4.9.95-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:   Thu, 19 Apr 2018 08:21:35 -0500
From:   Dan Rue <dan.rue@...aro.org>
To:     Naresh Kamboju <naresh.kamboju@...aro.org>
Cc:     Ben Hutchings <ben.hutchings@...ethink.co.uk>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        open list <linux-kernel@...r.kernel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Guenter Roeck <linux@...ck-us.net>,
        Shuah Khan <shuahkh@....samsung.com>, patches@...nelci.org,
        lkft-triage@...ts.linaro.org,
        linux- stable <stable@...r.kernel.org>,
        Ka-Cheong Poon <ka-cheong.poon@...cle.com>,
        Mark Rutland <mark.rutland@....com>
Subject: Re: [PATCH 4.9 00/66] 4.9.95-stable review

On Thu, Apr 19, 2018 at 06:00:52PM +0530, Naresh Kamboju wrote:
> On 19 April 2018 at 17:39, Ben Hutchings <ben.hutchings@...ethink.co.uk> wrote:
> > On Thu, 2018-04-19 at 16:42 +0530, Naresh Kamboju wrote:
> >> >
> >> > Can you try 'git bisect'?  I'll hold off on releasing 4.9.y until this
> >> > gets figured out.
> >>
> >> After reverting this patch, network started works on arm32 x15 device.
> >> d7ba3c00047d ("net: phy: micrel: Restore led_mode and clk_sel on resume")
> >
> > Does that also fix the hang during 'ip l'?  (If the hang only occurred
> > on the same systems that oops'd in the micrel driver, it could well be
> > because the task that oops'd was holding the rtnetlink lock.)
> 
> Now 'ip l' works and the oops message is gone.
> 
> - Naresh

There may be some confusion since this patch was in 4.9.94 and we did
not report this issue then. The way these failures presented themselves
made them a bit subtle (we didn't get any hard failures, just some
incomplete jobs - not an unusual occurrence on embedded boards) so we
didn't notice them in the last release. It was only after Naresh
manually investigated that this was discovered.

We'll think about how we can improve our process to make these much more
obvious in an automated way.

Dan