[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#885775: marked as done (apparmor: Apparmor triggers NULL pointer dereference in kernel 4.14.7-1 when updating with aptitude)

Your message dated Sun, 02 May 2021 02:44:26 -0700 (PDT)
with message-id <608e747a.1c69fb81.1fbc3.551d@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #885775,
regarding apparmor: Apparmor triggers NULL pointer dereference in kernel 4.14.7-1 when updating with aptitude
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
885775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885775
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apparmor
Version: 2.11.1-4
Severity: important

Dear Maintainer,


   * What led up to the situation?
	Installed kernel 4.14 in Debian Testing and ever since at every upgrade where systemd or other important 
	packages were upgraded the system froze with the last 2 lines in the system log:

	Dec 29 21:25:26 laca-desktop kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000005
	Dec 29 21:25:26 laca-desktop kernel: IP: __task_pid_nr_ns+0xc7/0xf0

	The system became unresponsive, not even the sysrq combinations were working
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
	Restarted ran dpkg --configure -a and every time the system froze
	Booting with the 4.13 kernel was fine, dpkg finished its run

	At the next upgrade i still got the freeze, after reboot i disabled the kernel security features with the kernel command line security=false

   * What was the outcome of this action?
	dpkg was working fine with the kernel 4.14 too


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (2, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages apparmor depends on:
ii  debconf [debconf-2.0]  1.5.65
ii  libc6                  2.25-5
ii  lsb-base               9.20170808
ii  python3                3.6.4~rc1-2

apparmor recommends no packages.

Versions of packages apparmor suggests:
ii  apparmor-profiles        2.11.1-4
pn  apparmor-profiles-extra  <none>
ii  apparmor-utils           2.11.1-4

-- debconf information excluded

--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: