linux-kernel - Re: [PATCH 4/4] parport: daisy: use new parport device model

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: <20191017211022.4247d821@gandalf.local.home>
Date:   Thu, 17 Oct 2019 21:10:22 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Sudip Mukherjee <sudipm.mukherjee@...il.com>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org, Michal Kubecek <mkubecek@...e.cz>
Subject: Re: [PATCH 4/4] parport: daisy: use new parport device model

On Wed, 16 Oct 2019 15:45:40 +0100
Sudip Mukherjee <sudipm.mukherjee@...il.com> wrote:

> Modify parport daisy driver to use the new parallel port device model.
> 
> Last attempt was '1aec4211204d ("parport: daisy: use new parport device
> model")' which failed as daisy was also trying to load the low level
> driver and that resulted in a deadlock.
> 
> Cc: Michal Kubecek <mkubecek@...e.cz>
> Cc: Steven Rostedt (VMware) <rostedt@...dmis.org>
> Signed-off-by: Sudip Mukherjee <sudipm.mukherjee@...il.com>
> ---
> 
> Steven, Michal,
> Can you please test this series in your test environment and verify that
> I am not breaking anything this time.
> 
>

I checked out 1aec4211204d~1 (just before the broken commit), and
applied these four patches. It booted with the config that wouldn't
boot with the broken commit.

Tested-by: Steven Rostedt (VMware) <rostedt@...dmis.org>

-- Steve