log_setup_kmod_log() is the function controlling verbocity level. When called from do_modprobe() execution path, it has a way to control the "log priority", being able to control how verbose the execution should be. Meanwhile, when log_setup_kmod_log() is called from do_depmod().. it has no way to control how verbose the rest of execution will be.
#define DEFAULT_VERBOSE LOG_WARNING
static int verbose = DEFAULT_VERBOSE;
and then:
depmod():
...
case 'v':
verbose++;
break;
...
log_setup_kmod_log(ctx, verbose);
...
since we have:
#define LOG_EMERG 0 /* system is unusable */
#define LOG_ALERT 1 /* action must be taken immediately */
#define LOG_CRIT 2 /* critical conditions */
#define LOG_ERR 3 /* error conditions */
#define LOG_WARNING 4 /* warning conditions */
#define LOG_NOTICE 5 /* normal but significant condition */
#define LOG_INFO 6 /* informational */
#define LOG_DEBUG 7 /* debug-level messages *
Something is bumping the verbose from "warning" into "debug" automatically.
Here is the thing...
log_setup_ kmod_log( ) is the function controlling verbocity level. When called from do_modprobe() execution path, it has a way to control the "log priority", being able to control how verbose the execution should be. Meanwhile, when log_setup_ kmod_log( ) is called from do_depmod().. it has no way to control how verbose the rest of execution will be.
#define DEFAULT_VERBOSE LOG_WARNING
static int verbose = DEFAULT_VERBOSE;
and then:
depmod(): kmod_log( ctx, verbose);
...
case 'v':
verbose++;
break;
...
log_setup_
...
since we have:
#define LOG_EMERG 0 /* system is unusable */
#define LOG_ALERT 1 /* action must be taken immediately */
#define LOG_CRIT 2 /* critical conditions */
#define LOG_ERR 3 /* error conditions */
#define LOG_WARNING 4 /* warning conditions */
#define LOG_NOTICE 5 /* normal but significant condition */
#define LOG_INFO 6 /* informational */
#define LOG_DEBUG 7 /* debug-level messages *
Something is bumping the verbose from "warning" into "debug" automatically.