linux-kernel - Re: [PATCH] component: remove device from master match list on failed add

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:	Mon, 15 Feb 2016 16:36:55 +0000
From:	Daniel Stone <daniel@...ishbar.org>
To:	Akshay Bhat <akshay.bhat@...esys.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Russell King - ARM Linux <linux@....linux.org.uk>,
	dri-devel <dri-devel@...ts.freedesktop.org>
Subject: Re: [PATCH] component: remove device from master match list on failed add

Russell,

On 12 February 2016 at 00:57, Akshay Bhat <akshay.bhat@...esys.com> wrote:
> Daniel Stone <daniels <at> collabora.com> writes:
>> Fixes: ffc30b74fd6d01588bd3fdebc3b1acc0857e6fc8
>> Signed-off-by: Daniel Stone <daniels <at> collabora.com>
>
> Tested-by: Akshay Bhat <akshay.bhat@...esys.com>
>
> Tested on imx6 processor based board where re-probe was broken after a
> probe deferral.

One-week ping; this breaks quite a few drivers, even despite
57480484f9 already being present. Another option could just be to
revert the original match-array commit (and the subsequent two fixups)
until you can work out a fix.

Cheers,
Daniel