← Back to team overview

desktop-packages team mailing list archive

[Bug 1433320] Re: systemd-journald, udev, logind crashed with SIGABRT -- get killed by 1 min watchdog timeout on longer kernel lockups

 

This bug was fixed in the package apport - 2.19-0ubuntu1

---------------
apport (2.19-0ubuntu1) wily; urgency=medium

  * New upstream release:
    - apport: Drop re-nicing. This might decrease the time a user has to wait
      for apport to finish the core dump for a crashed/hanging foreground
      process.  (See LP #1278780)
    - kernel_crashdump: Enforce that the log/dmesg files are not a symlink.
      This prevents normal users from pre-creating a symlink to the
      predictable .crash file, and thus triggering a "fill up disk" DoS attack
      when the .crash report tries to include itself. Thanks to halfdog for
      discovering this!  (CVE-2015-1338, part of LP #1492570)
    - SECURITY FIX: Fix all writers of report files (package_hook,
      kernel_crashdump, and similar) to open the report file exclusively,
      i. e.  fail if they already exist. This prevents privilege escalation
      through symlink attacks. Note that this will also prevent overwriting
      previous reports with the same same. Thanks to halfdog for discovering
      this!  (CVE-2015-1338, LP: #1492570)
    - apport: Ignore process restarts from systemd's watchdog. Their traces
      are usually useless as they don't have any information about the actual
      reasaon why processes hang (like VM suspends or kernel lockups with bad
      hardware) (LP: #1433320)

 -- Martin Pitt <martin.pitt@xxxxxxxxxx>  Thu, 24 Sep 2015 14:41:54
+0200

** Changed in: apport (Ubuntu)
       Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-1338

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1433320

Title:
  systemd-journald, udev, logind crashed with SIGABRT -- get killed by 1
  min watchdog timeout on longer kernel lockups

Status in apport package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Errors Bucket
  -------------
  https://errors.ubuntu.com/bucket/?id=/lib/systemd/systemd-journald%3A6%3A__epoll_wait_nocancel%3Asd_event_wait%3Asd_event_run%3Amain

  
  Sometimes userspace get locked up hard: A QEMU instance sees long hangs while the host gets suspended, USB devices/drivers lock up for some time (like in this bug's dmesg), or Google hangouts in bug 1495585.
  The kernel detects that some process(es) get hard-locked up, the hardware watchdog (which systemd configures for some crucial services to auto-restart them via "WatchdogSec=1min") picks this up and restarts the process. 

  In that case, these crash reports only describe the symptom, not the
  cause. They should be suppressed since they provide no information
  that can be used to diagnose the actual root problem.


  
  ProblemType: CrashDistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1
  Uname: Linux 3.19.0-8-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  Date: Tue Mar 17 17:18:08 2015
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2014-02-24 (386 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-8-generic root=UUID=7f776823-8240-460b-ab2d-45c8a2b2f2b6 ro quiet splash
  Signal: 6SourcePackage: systemd
  StacktraceTop:
   __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81
   ?? ()
   ?? ()
   __libc_start_main (main=0x7f94ef54c760, argc=1, argv=0x7ffe7c6e2fa8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe7c6e2f98) at libc-start.c:287
   ?? ()
  Title: systemd-journald crashed with SIGABRT in __epoll_wait_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 05/20/2014
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1433320/+subscriptions