linux-kernel - Re: [char-misc-next] mei: hook mei

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <501acd49-b8ab-4fd4-85d3-79ca3deca034@roeck-us.net>
Date: Sun, 2 Nov 2025 07:14:31 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: "Usyskin, Alexander" <alexander.usyskin@...el.com>
Cc: Marek Marczykowski-Górecki <marmarek@...isiblethingslab.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"Abliyev, Reuven" <reuven.abliyev@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [char-misc-next] mei: hook mei_device on class device

On Sun, Nov 02, 2025 at 10:12:56AM +0000, Usyskin, Alexander wrote:
...
> 
> Seems I've missed the error flow in probe (my test machines always have an ME in a good state...).
> 
> Below patch should fix the problem, can you confirm?

testing.

Thanks!

Guenter