Bug 258749 - /etc/defaults/rc.conf says devmatch_blacklist doesn't need .ko, but it does
Summary: /etc/defaults/rc.conf says devmatch_blacklist doesn't need .ko, but it does
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: conf (show other bugs)
Version: 13.0-STABLE
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-27 18:11 UTC by mwlucas
Modified: 2021-09-27 18:27 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mwlucas 2021-09-27 18:11:09 UTC
Not sure what the correct behavior is, so I'm pointing out the inconsistency and letting y'all decide. /etc/defaults/rc.conf says:

devmatch_blacklist=""   # List of modules (w/o .ko) to exclude from devmatch.

This appears to be incorrect.

Thanks to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253175 I had to disable virtio_random on my new VM at install time. I set

devmatch_blacklist="virtio_random"

and the module was loaded anyway.

devmatch_blacklist="virtio_random.ko" prevented the module from being loaded.

So, either the script is working wrong or the comment is incorrect.

I checked rc.conf(5) for a tiebreaker, but it doesn't specifically mention .ko.
Comment 1 Thomas Hurst 2021-09-27 18:27:40 UTC
Duplicate of https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256240 - fixed in https://cgit.freebsd.org/src/commit/?id=b29ebb9c65b350e78aedfc790bfcaf9717059b70 and merged to stable/12 and 13.