Page MenuHomeFreeBSD

linuxkpi/dmi: don't match exactly on DMI_MATCH
ClosedPublic

Authored by corvink on Jun 3 2022, 2:17 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Oct 10, 2:29 AM
Unknown Object (File)
Fri, Oct 10, 2:29 AM
Unknown Object (File)
Fri, Oct 10, 2:28 AM
Unknown Object (File)
Thu, Oct 9, 9:46 PM
Unknown Object (File)
Mon, Sep 22, 9:59 PM
Unknown Object (File)
Sep 14 2025, 2:16 PM
Unknown Object (File)
Sep 9 2025, 1:36 AM
Unknown Object (File)
Sep 4 2025, 4:44 PM

Details

Summary

Linux has two defines to check dmi data. DMI_MATCH checks if the dmi
string includes substr. DMI_EXACT_MATCH checks if the dmi string exactly
matches substr. Compat layer should have the same behaviour.

The new definition of dmi_strmatch shouldn't break any driver. A driver
would break if it uses the highest bit of the slot field. Nevertheless,
linux uses the same definition and FreeBSD uses dmi_field values as slot
which are lower than 128.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable