Segfault on startup

Bug #1102196 reported by Bilge
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
ntp (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

When starting ntpd it segfaults almost straight away. The configuration is the default that ships with Ubuntu 12.04.1 LTS.

23:25:51 ntpd[18123]: ntpd 4.2.6p3@1.2290-o Tue Jun 5 20:12:08 UTC 2012 (1)
23:25:51 ntpd[18124]: proto: precision = 0.352 usec
23:25:51 ntpd[18124]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
23:25:51 ntpd[18124]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
23:25:51 ntpd[18124]: Listen and drop on 1 v6wildcard :: UDP 123
23:25:51 ntpd[18124]: Listen normally on 2 lo 127.0.0.1 UDP 123
23:25:51 ntpd[18124]: Listen normally on 3 eth0 1.2.3.4 UDP 123
23:25:51 ntpd[18124]: Listen normally on 4 eth0:0 5.6.7.8 UDP 123
23:25:51 ntpd[18124]: Listen normally on 5 eth0 fe80::1 UDP 123
23:25:51 ntpd[18124]: Listen normally on 6 eth0 2001::2 UDP 123
23:25:51 ntpd[18124]: Listen normally on 7 eth0 2001::1 UDP 123
23:25:51 ntpd[18124]: Listen normally on 8 lo ::1 UDP 123
23:25:51 ntpd[18124]: peers refreshed
23:25:51 ntpd[18124]: Listening on routing socket on fd #25 for interface updates
23:25:52 ntpd[18124]: Deleting interface #8 lo, ::1#123, interface stats: received=0, sent=0, dropped=0, active_time=1 secs
23:25:52 ntpd[18124]: Deleting interface #7 eth0, 2001::1#123, interface stats: received=0, sent=0, dropped=0, active_time=1 secs
23:25:52 ntpd[18124]: Deleting interface #6 eth0, 2001::2#123, interface stats: received=0, sent=0, dropped=0, active_time=1 secs
23:25:52 ntpd[18124]: 2001::3 interface 2001::2 -> (none)
23:25:52 kernel: ntpd[18124]: segfault at 8 ip 00007f6df3ecee5e sp 00007fff1df448a0 error 4 in ntpd[7f6df3eb1000+97000]
23:25:52 kernel: grsec: From 9.10.11.12: Segmentation fault occurred at 0000000000000008 in /usr/sbin/ntpd[ntpd:18124] uid/euid:108/108 gid/egid:115/115, parent /sbin/init[init:1] uid/euid:0/0 gid/egid:0/0

Tags: segfault
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Thanks for reporting this bug. It is a result of a lock in liblockfile. I will mark this bug a dup of bug 941968. I've also bumped the priority of that bug to high to hopefully get the proposed patch to fix it reviewed faster.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ntp (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.