linux-kernel - Re: [ppdev] e7223f1860: kernel BUG at drivers/base/driver.c:153!

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: <CA+55aFwBajpyGXHbRA79xfDJ449nX+38M6gwxwEw-A2ES4MHYQ@mail.gmail.com>
Date:	Fri, 25 Mar 2016 09:12:26 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Petr Mladek <pmladek@...e.com>
Cc:	Sudip Mukherjee <sudipm.mukherjee@...il.com>,
	kernel test robot <fengguang.wu@...el.com>, LKP <lkp@...org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	wfg@...ux.intel.com
Subject: Re: [ppdev] e7223f1860: kernel BUG at drivers/base/driver.c:153!

On Thu, Mar 24, 2016 at 7:41 AM, Petr Mladek <pmladek@...e.com> wrote:
>
> Could we please get the fix into the mainline?

I've reverted the offending original commit for now. The fix I see
seems questionable - just ignoring the parport registration will get
rid of the oops, but drivers shouldn't be testing that "p" value
anyway, and it also fundamentally seems to just drop the parport
registration on the floor, so it doesn't seem like a real fix anyway.

So reverting the whole mess seems like the right thing. It's triply
the right thing when it's over a month since the original report, and
this shit made it into my kernel anyway.

Not acceptable.

             Linus