[Bug 1982555] Re: core dump file empty inside container
Launchpad Bug Tracker
1982555 at bugs.launchpad.net
Sat Aug 27 20:26:30 UTC 2022
This bug was fixed in the package apport - 2.23.0-0ubuntu1
---------------
apport (2.23.0-0ubuntu1) kinetic; urgency=medium
* New upstream release:
- apport-gtk:
- Gracefully handle import failure of gi (LP: #1980561)
- Catch AssertionError when importing Gdk (LP: #1980238)
- data/apport:
- Fix PermissionError for setuid programs inside container (LP: #1982487)
- Fix reading from stdin inside containers (LP: #1982555)
- apport-kde:
- Fix inverse order of choices (LP: #1967965)
- Import apport before usage (LP: #1980553)
- Drop old workaround for bug in SIP destructor (LP: #1980553)
- apport-unpack: Fix ValueError: ['separator'] has no binary content
(LP: #1889443)
- Fix _run_hook getting called with ui=None (LP: #1983481)
* Refresh patches and drop backported patches
* Fix pydocstyle and pylint complains in patches
-- Benjamin Drung <bdrung at ubuntu.com> Mon, 22 Aug 2022 22:31:55 +0200
** Changed in: apport (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1982555
Title:
core dump file empty inside container
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Focal:
Confirmed
Status in apport source package in Jammy:
Confirmed
Bug description:
[Impact]
Apport will write an empty core dump file inside of containers.
[Test plan]
Run following testcase script inside a LXC container:
```
rm -f /var/lib/apport/coredump/*
ulimit -c 1000000
sleep 86400 &
killall -3 sleep
```
Apport will write a core dump into /var/lib/apport/coredump, but this
core dump is empty:
```
$ stat /var/lib/apport/coredump/core._usr_bin_sleep.*
File: /var/lib/apport/coredump/core._usr_bin_sleep.0.44f483a1-e487-44b3-88d1-805d1026f31d.9059.34839819
Size: 0 Blocks: 0 IO Block: 4096 regular empty file
Device: fd00h/64768d Inode: 120848663 Links: 1
Access: (0400/-r--------) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2022-07-22 07:54:48.838682067 +0000
Modify: 2022-07-22 07:54:48.838682067 +0000
Change: 2022-07-22 07:54:48.838682067 +0000
Birth: 2022-07-22 07:54:48.838682067 +0000
```
This file should not be empty.
[Where problems could occur]
The apport binary is called by the kernel when a process crashes.
Worst case scenarios include breaking the apport binary and no problem
report is generated any more (or apport uses too much resources).
Users will see problems reports inside the container which cause
additional load or disk usage. The fix is accompanied by a test case.
[Other Info]
The autopkgtest for armhf are run inside a LXC container and the test
case test_core_dump_packaged_sigquit triggers this bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1982555/+subscriptions
More information about the foundations-bugs
mailing list