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)
Thu, Mar 13, 11:25 PM
Unknown Object (File)
Thu, Mar 13, 5:33 PM
Unknown Object (File)
Thu, Mar 6, 4:35 PM
Unknown Object (File)
Thu, Mar 6, 12:38 PM
Unknown Object (File)
Feb 26 2025, 10:46 AM
Unknown Object (File)
Feb 26 2025, 6:05 AM
Unknown Object (File)
Feb 25 2025, 11:26 PM
Unknown Object (File)
Feb 25 2025, 10:28 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