linux-kernel - Re: [char-misc-next v3 1/5] mei: set parent for char device

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: <2025071614-approach-snarl-90d7@gregkh>
Date: Wed, 16 Jul 2025 11:47:09 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Alexander Usyskin <alexander.usyskin@...el.com>
Cc: Reuven Abliyev <reuven.abliyev@...el.com>, linux-kernel@...r.kernel.org
Subject: Re: [char-misc-next v3 1/5] mei: set parent for char device

On Wed, Jul 09, 2025 at 06:13:40PM +0300, Alexander Usyskin wrote:
> Connect char device to parent device to avoid
> parent device unload while char device is
> still held open by user-space.

Again, this changelog text is not right.  The parent pointer has nothing
to do with "unloading" anything.  It has everything to do with placing
the device in the proper place in sysfs.  So please show a before/after
location of what happens when this patch is applied to make it more
obvious what is happening here.

thanks,

greg k-h