01.02.2019 0:52, Jeff Mahoney пишет:
On 1/31/19 4:05 PM, Carlos E. R. wrote:
Ideally, the mount command would print information, or where to read more.
The mount command doesn't have that context. It calls mount(2) and the kernel requests that userspace load the module. Then mount(2) returns -ENODEV, which is documented in the mount(2) man page as "file system type not configured in the kernel." If the module isn't loaded, the module doesn't register as a file system type, and then there's no difference between "mount -t sadlksjadlk" and "mount -t jfs".
modprobe could return dedicated exit code to indicate "module is blacklisted". request_module() returns exit code of user helper so it would return this error to caller. Caller (mount layer) currently ignores return value of request_module(), so it would need change to use and return it. Currently list of blacklisted modules is maintained in one package, list of modules for which to print warnings in another package (in different format) which almost inevitably leads to them differ over time. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org