From 762bb042ec4aeea41029208ef2d25e3919a23ae2 Mon Sep 17 00:00:00 2001 From: Sylvain Munaut Date: Fri, 10 May 2019 11:56:02 +0200 Subject: make LOG_TRANS() NULL-safe again Previous patch [1] removed NULL-safety from LOG_TRANS(). Fix that. In case a trans is NULL, it is fine to log in the DMSC category, since the context should still be general (erratic message or other initial problems). [1] 7f85acea9bb9f80e208820958f4cae63625f3689 / I6dfe5b98fb9e884c2dde61d603832dafceb12123 "LOG_TRANS: store subsys in trans, unify USSD logging back to DMM" Change-Id: I6e36c47bf828dd073b36c6301bbeabcc28e101e6 --- include/osmocom/msc/transaction.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'include') diff --git a/include/osmocom/msc/transaction.h b/include/osmocom/msc/transaction.h index c63ef5bc7..9278b6400 100644 --- a/include/osmocom/msc/transaction.h +++ b/include/osmocom/msc/transaction.h @@ -27,7 +27,7 @@ struct vty; ##args) #define LOG_TRANS(trans, level, fmt, args...) \ - LOG_TRANS_CAT(trans, (trans)->log_subsys, level, fmt, ##args) + LOG_TRANS_CAT(trans, (trans) ? (trans)->log_subsys : DMSC, level, fmt, ##args) enum bridge_state { BRIDGE_STATE_NONE, -- cgit v1.2.3