Bart, > Are you perhaps referring to the five __force casts? If so, do you > have a suggestion for avoiding that sparse reports false positive > warnings on the conversions between int and blist_flags_t? The only > approach I can think of to reduce the number of __force casts is to > embed these __force casts into two helper functions - one for the > conversion from int to blist_flags_t and one for the conversion the > other way around. blist_flags_t is an unsigned int, you are forcing it to u32 two places. That's a problem waiting to happen next time we add a blacklist flag. -- Martin K. Petersen Oracle Linux Engineering
