Filling dummy module's hook to null value of xsm_operations structure will generate debug message. This becomes boot time spew for module like silo, which only sets a few hooks of itself. So remove the printing to avoid boot time spew.
Signed-off-by: Xin Li <[email protected]> --- CC: Daniel De Graaf <[email protected]> CC: George Dunlap <[email protected]> CC: Jan Beulich <[email protected]> CC: Konrad Rzeszutek Wilk <[email protected]> CC: Stefano Stabellini <[email protected]> CC: Tim Deegan <[email protected]> CC: Wei Liu <[email protected]> CC: Sergey Dyasli <[email protected]> CC: Andrew Cooper <[email protected]> CC: Ming Lu <[email protected]> v5: 1. new change to avoid boot time spew. --- xen/xsm/dummy.c | 5 ----- 1 file changed, 5 deletions(-) diff --git a/xen/xsm/dummy.c b/xen/xsm/dummy.c index 06a674fad0..5701047c06 100644 --- a/xen/xsm/dummy.c +++ b/xen/xsm/dummy.c @@ -18,12 +18,7 @@ struct xsm_operations dummy_xsm_ops; #define set_to_dummy_if_null(ops, function) \ do { \ if ( !ops->function ) \ - { \ ops->function = xsm_##function; \ - if (ops != &dummy_xsm_ops) \ - dprintk(XENLOG_DEBUG, "Had to override the " #function \ - " security operation with the dummy one.\n"); \ - } \ } while (0) void __init xsm_fixup_ops (struct xsm_operations *ops) -- 2.18.0 _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
