lapd: Always print context information when logging
Historically, OpenBSC has primarily been used with setups that have
a single E1 based BTS connected. This meant that an error message on
the E1 LAPD implicitly has to be related to that single BTS.
However, in more comprehensive setups, there may be many BTSs on many
E1 lines with many signaling slots. At this point, it's important to
know which line/timeslot/tei/sapi a given log message relates to.
This patch introduces related log context.
Change-Id: Ib81a749ae24013b17caaf5fd64ccd9acbbc3ce08
Requires: libosmocore.git Change-Id Ie6742843fff809edffcac24c4dce4edf66bc71be
Related: OS#1938
diff --git a/src/input/misdn.c b/src/input/misdn.c
index fef1c0f..564d008 100644
--- a/src/input/misdn.c
+++ b/src/input/misdn.c
@@ -636,10 +636,12 @@
switch (e1i_ts->type) {
case E1INP_TS_TYPE_SIGN:
if (mline->use_userspace_lapd) {
+ char name[32];
addr.channel = ts;
- e1i_ts->lapd = lapd_instance_alloc(1,
+ e1inp_ts_name(name, sizeof(name), e1i_ts);
+ e1i_ts->lapd = lapd_instance_alloc2(1,
misdn_write_msg, bfd, e1inp_dlsap_up,
- e1i_ts, &lapd_profile_abis);
+ e1i_ts, &lapd_profile_abis, name);
} else {
addr.channel = 0;
/* SAPI not supported yet in kernel */