linux-kernel - Re: [PATCH v2] parport: register driver later

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: <CA+55aFxaXhSp9+Fa09rKHVge5-epMsEZsyyChmbRjPS=ohb-Sg@mail.gmail.com>
Date:	Tue, 5 Apr 2016 06:44:12 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	Sudip Mukherjee <sudipm.mukherjee@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	stable <stable@...r.kernel.org>,
	Ross Zwisler <ross.zwisler@...ux.intel.com>
Subject: Re: [PATCH v2] parport: register driver later

On Tue, Apr 5, 2016 at 5:58 AM, Greg KH <gregkh@...uxfoundation.org> wrote:
>
> A bit better commit message here would have caused me to notice it.
> Something like "Revert a broken patch because it crashes all of our
> machines without it!!!" would be a hint it needed to go in :)

Didn't my revert of e7223f1860 fix this?

> I think the lack of parport hardware around seems to have caused a total
> lack of testing this code path while it was in linux-next and in my
> local testing, sorry about that, it should have been caught a lot
> earlier.

Well, the original 0day kernel test robot report was from the
linux-next days, back in February. I reverted the commit that the
kernel test robot indicated was the point where the actual trouble
started two weeks ago (commit 1701f680407c).

I was hoping that would be it. Have there been reports since that I
haven't seen?

                Linus