btrfs-progs: introduce more message levels

Add more granularity to verbose levels and describe when they should be
used. Lots of pr_verbose still hardcode the value or compare level to
bconf.verbose but the individual messages have to be revisited
separately.

Signed-off-by: David Sterba <dsterba@suse.com>
This commit is contained in:
David Sterba 2022-09-29 17:33:29 +02:00
parent 9150cdd7e6
commit 77787d12d5

View File

@ -108,7 +108,24 @@ void internal_error(const char *fmt, ...);
* options haven't been set by the user) due to backward compatibility reasons
* where applications may expect the output.
*/
#define LOG_ALWAYS -1
#define LOG_ALWAYS (-1)
/*
* Default level for any messages that should be printed by default, a one line
* summary or with more details. Applications should not rely on such messages.
*/
#define LOG_DEFAULT (1)
/*
* Information about the ongoing actions, high level description
*/
#define LOG_INFO (2)
/*
* Verbose description and individual steps of the previous level
*/
#define LOG_VERBOSE (3)
/*
* Anything that should not be normally printed but can be useful for debugging
*/
#define LOG_DEBUG (4)
__attribute__ ((format (printf, 2, 3)))
void pr_verbose(int level, const char *fmt, ...);