linux-kernel - Convert type of 'struct dmi_system_id -> driver_data' from 'void *' to kernel_ulong

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: <CAAd53p5EiTXfAhCFPDaicksQOa5usOkS5v7moPgM2A7QZ6QCqg@mail.gmail.com>
Date:   Wed, 19 Jan 2022 09:22:43 +0800
From:   Kai-Heng Feng <kai.heng.feng@...onical.com>
To:     LKML <linux-kernel@...r.kernel.org>
Cc:     jkosina@...e.cz, Hans de Goede <hdegoede@...hat.com>,
        Jason Gunthorpe <jgg@...pe.ca>,
        Bjorn Helgaas <bhelgaas@...gle.com>, mgurtovoy@...dia.com,
        linux@...ssschuh.net, Arnd Bergmann <arnd@...db.de>,
        stephan@...hold.net, "Rafael J. Wysocki" <rafael@...nel.org>
Subject: Convert type of 'struct dmi_system_id -> driver_data' from 'void *'
 to kernel_ulong_t?

Hi,

I wonder if there's any reason to use 'void *' instead of
kernel_ulong_t for 'driver_data' in 'struct dmi_system_id'?

I'd like to use the driver_data for applying quirk flags, and I found
out unlike most other struct *_id, the dmi variant is using 'void *'
for driver_data. Is there any technical reason for this?

Kai-Heng