log: Add filter flag to deny on match

Without this flag, log filters can only explicitly accept messages.
Allowing denial makes it easier to filter certain subsystems. Unlike
allow-ing filters, deny-ing filters are added to the beginning of the
filter list. This should do the Right Thing most of the time, but it's
less-universal than allowing filters to be inserted anywhere. If this
becomes a problem, then perhaps log_filter_add* should take a filter number
to insert before/after.

Signed-off-by: Sean Anderson <seanga2@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
This commit is contained in:
Sean Anderson 2020-10-27 19:55:26 -04:00 committed by Tom Rini
parent a02f84ee9c
commit fe3b1a2d21
2 changed files with 20 additions and 3 deletions

View file

@ -361,13 +361,22 @@ enum {
LOGF_MAX_CATEGORIES = 5, /* maximum categories per filter */
};
/**
* enum log_filter_flags - Flags which modify a filter
*/
enum log_filter_flags {
LOGFF_HAS_CAT = 1 << 0, /* Filter has a category list */
/** @LOGFF_HAS_CAT: Filter has a category list */
LOGFF_HAS_CAT = 1 << 0,
/** @LOGFF_DENY: Filter denies matching messages */
LOGFF_DENY = 1 << 1,
};
/**
* struct log_filter - criterial to filter out log messages
*
* If a message matches all criteria, then it is allowed. If LOGFF_DENY is set,
* then it is denied instead.
*
* @filter_num: Sequence number of this filter. This is returned when adding a
* new filter, and must be provided when removing a previously added
* filter.