linux-kernel - exporting a device type

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-next>] [day] [month] [year] [list]

Message-ID: <CAHp75VdssCM74oji59QjPMEzrVuBzPOAMadA=Ds_52hOZGJ2mw@mail.gmail.com>
Date: Fri, 11 Apr 2025 22:39:38 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Danilo Krummrich <dakr@...nel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: exporting a device type

I have an issue with this change

https://web.git.kernel.org/pub/scm/linux/kernel/git/dakr/linux.git/commit/?h=for-driver-core&id=e86cc69186051d7312711565803de586efd9b2cf

(I think you haven't yet sent it for review, so this is just
preliminary look at)

The idea of exporting bus type will open a non-reversible box of
changes when people will start abusing it. Instead just provide an API
dev_is_auxiliary() as it's done in other subsystems (yes, I know that
some of them are still exporting the type, but it's most likely due to
historical reasons of not thinking through it at that time).

-- 
With Best Regards,
Andy Shevchenko