Source: apparmor Severity: important Dear Maintainer, when apparmor is installed, it emits an incredible amount of logs on dmesg, causing actual important stuff from the kernel to be missed.
By incredible amount I mean that it fills completely the ring buffer with crap. Should it even be logging on dmesg? Imagine dmesg, only filled of this: [299560.719237] audit: type=1400 audit(1541071734.314:10526): apparmor="DENIED" operation="ptrace" profile="firejail-default" pid=13691 comm="TaskSchedulerSi" requested_mask="read" denied_mask="read" peer="firejail-default" [299560.719241] audit: type=1400 audit(1541071734.314:10527): apparmor="DENIED" operation="ptrace" profile="firejail-default" pid=13691 comm="TaskSchedulerSi" requested_mask="readby" denied_mask="readby" peer="firejail-default" [299560.921678] audit: type=1400 audit(1541071734.518:10528): apparmor="DENIED" operation="ptrace" profile="firejail-default" pid=13691 comm="TaskSchedulerSi" requested_mask="read" denied_mask="read" peer="firejail-default" For now my solution is to remove apparmor, but it gets sometimes pulled in again by other things. Best -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to it_IT.UTF-8), LANGUAGE=it (charmap=UTF-8) (ignored: LC_ALL set to it_IT.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
