Project

General

Profile

Actions

Bug #3217

closed

osmo-ggsn crashes during start-up when using kernel GTP-U

Added by laforge almost 6 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
-
Target version:
-
Start date:
04/25/2018
Due date:
% Done:

100%

Spec Reference:

Description

When starting up osmo-ggsn, we're seeing segfaults.

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
<0002> ggsn.c:203 APN(S1U): Starting
<0002> ggsn.c:281 APN(S1U): Opening Kernel GTP device gtp0
<0002> gtp-kernel.c:75 Initialized GTP kernel mode (genl ID is 30)

Program received signal SIGSEGV, Segmentation fault.
gtp_kernel_init (gsn=0x0, devname=0x6a6fe0 "gtp0",
    prefix=prefix at entry=0x6a76e0, ipup=0x0) at gtp-kernel.c:94
94 if (gtp_dev_create(-1, devname, gsn->fd0, gsn->fd1u) < 0) {

See http://lists.osmocom.org/pipermail/osmocom-net-gprs/2018-April/001019.html for more info.

Actions #1

Updated by laforge almost 6 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 80

The underlying isuse here is that there's a problem during the initial start-up of osmo-ggsn in case of kernel gtp-u: apn->ggsn->gsn is not yet set while parsing the 'apn' nodes from the config file. This member is only set after the last 'apn' node has been parsed at the end of the 'ggsn' node.

So what we now do is we basically skip the initialization during reading of the 'apn' nodes, as the GGSN startup at the bottom of the config will bring any non-disabled APNs anyway. See https://gerrit.osmocom.org/7919 for a related fix.

Actions #2

Updated by laforge almost 6 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 80 to 100

patch merged

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)