[`lsmod`] '-v' option not operational

[Ricky-Tigg]

kmod version 34.2 | +ZSTD +XZ +ZLIB +LIBCRYPTO

Hello. The outputs of 'lsmod' are identical whether the '-v' option is part of the command or not, which indicates that the option is not operational since expected to cause verbosity.

[evelikov]

The default verbosity level of all kmod commands is LOG_ERR, where each -v instance increases it up a level - LOG_INFO, LOG_NOTICE, LOG_DEBUG.

Perhaps our man/help pages should be updated to illustrate that more clearly? Patches are welcome.

[Ricky-Tigg]

Enhancement opportunities

• This is yet another aspect that is both specific and essential, which you have highlighted. It's amusing that its omission from the LSMOD(8) man-page could have gone unnoticed. This context clearly warrants a re-evaluation of the current definition. For example, does "Usually lsmod prints messages only if something goes wrong." now refer to the LOG_ERR instruction?

• It is worth noting that the code not only tolerates a number of '-v' instances superior than the actual number of specifications, 4 then, but does so without indicating in the output that only four levels of verbosity are supported, which corresponds to the '-vvvv' option.

Issue

Thanks to your revelation here, an issue can be determined now.

Steps to reproduce

• Invoke the '-vv option', which corresponds to the LOG_INFO instruction.

result: No matches as "lsmod: INFO:" printed.

However, matches do exist, as the following demonstrates.

• Invoke the '-vvv', '-vvvv' options

result: Matches as "lsmod: INFO:" printed.