[Bug 1982555] Re: core dump file empty inside container

[Timo Aaltonen]

Hello Benjamin, or anyone else affected,

Accepted apport into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.11-0ubuntu27.25 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed-focal

-- 
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:
  Fix Committed
Status in apport source package in Jammy:
  Fix Committed

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.

  Due to the huge amount of broken autopkgtest tests, the diff for the
  SRUs are bigger than desired. The individual commits in
  https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/ are
  probably easier to review.

  * jammy SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=1fa042cc27714c407494b3d6dfd0730bb984f3eb
  * focal SRU: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/apport/log/?h=eaa92037c7dfba621719c6f81fd75f6a09e90881

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