Is _only_ srcname being corrupted? Back In The Day it was common for the kernel ring buffer for messages to overflow and overwrite messages, but of course it did not care what was being overwritten.
The kernel ring buffer is larger now, so it should be less common, but not impossible if the logging device is too slow to keep up with the rate of message generation. If log messages must be kept intact, perhaps auditd makes more sense. Or is something else going on? Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1634753 Title: srcname from mount rule corrupted under load Status in AppArmor: In Progress Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Yakkety: Triaged Bug description: This came up in snapd spread tests but can be reproduced with: In an i386 up to date 16.04 VM: 1. in one terminal, run this: $ cat changehat_reproducer.sh #!/bin/sh set -e sudo sysctl -w kernel.printk_ratelimit=0 sudo snap install hello-world || true count=0 while /bin/true ; do count=$((count+1)) if [ `echo "$count % 100" | bc` -eq 0 ]; then echo "$count runs" fi hello-world > /dev/null || { tail -100 /var/log/syslog | grep DEN && exit } sudo cat /run/snapd/ns/hello-world.mnt 2>/dev/null || sudo /usr/lib/snapd/snap-discard-ns hello-world done 2. in another terminal run: $ while do /bin/true ; sudo apparmor_parser -r /etc/apparmor.d/* >/dev/null 2>&1 ; done 3. In another terminal: $ tail -f /var/log/syslog|grep DEN This is not limited to i386. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1634753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
