[Xen-changelog] [xen master] xsm: remove printing from set_to_dummy_if_null()

[p***@xen.org]

commit d78e52da2dff699e4ac0142901adaba41031509c
Author: Xin Li <***@citrix.com>
AuthorDate: Fri Nov 9 11:41:30 2018 +0100
Commit: Jan Beulich <***@suse.com>
CommitDate: Fri Nov 9 11:41:30 2018 +0100

xsm: remove printing from set_to_dummy_if_null()

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.

Reported-by: Andrew Cooper <***@citrix.com>
Signed-off-by: Xin Li <***@citrix.com>
Acked-by: Daniel De Graaf <***@tycho.nsa.gov>
---
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)
--
generated by git-patchbot for /home/xen/git/xen.git#master