|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [PATCH v2 1/7] tools/xenalyze: Fix -Werror=nonnull failure
GCC 15.2 with Alpine Linux 3.24 fails with -Werror=nonnull, complaining that we're calling bzero(NULL, 128). This is a legitimate diagnostic. xenalyze has it's own error() function shadowing the standard library one, and can in principle return when p is NULL. Extend the check in error() with ERR_MAX_TOLERABLE to short circuit the variable tolerance check. Suggested-by: Anthony PERARD <anthony.perard@xxxxxxxxxx> Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Release-Acked-by: Oleksii Kurochko <oleksii.kurochko@xxxxxxxxx> --- v2: * Fix in light of error() being local https://gitlab.com/xen-project/hardware/xen-staging/-/pipelines/2602806440 --- tools/xentrace/xenalyze.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/xentrace/xenalyze.c b/tools/xentrace/xenalyze.c index 876d59d42ca5..42feeb282e31 100644 --- a/tools/xentrace/xenalyze.c +++ b/tools/xentrace/xenalyze.c @@ -8767,7 +8767,7 @@ void dump_raw(const char * s, struct record_info *ri) void error(enum error_level l, struct record_info *ri) { - if ( l > opt.tolerance ) + if ( l > ERR_MAX_TOLERABLE || l > opt.tolerance ) { if ( ri ) dump_generic(warn, ri); -- 2.39.5
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |