From: Patrick Talbert on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2606#note_1490800627 Sure, I wasn't intending to block this MR for this idea. Though I would argue that output from sysfs is pretty clearly only directly relevant to the kernel which produced it. I don't see why anybody would think a module being listed in this proposed sysfs entry is indicative of anything more than what is said in the message they see in the logs when they load that module. Heck, the first line of the sysfs output could be a # followed by the same blurb we're going to output when they load any of the given modules 🤷. I guess my point is if a customer loads an affected module and sees a warning they very well may want to know what other modules may be affected on that system and they won't have a clear way of seeing it. _______________________________________________ kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
