kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #187404
[Bug 1378123] Re: unix_socket_abstract.sh triggers an AppArmor WARN
I cannot reproduce this with linux-generic-lts-xenial. I think it is
safe to say that this bug was fixed in 16.04.
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Vivid)
Status: New => Confirmed
** Changed in: linux (Ubuntu Wily)
Status: New => Confirmed
** Changed in: linux (Ubuntu Xenial)
Status: New => Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
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/1378123
Title:
unix_socket_abstract.sh triggers an AppArmor WARN
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Vivid:
Confirmed
Status in linux source package in Wily:
Confirmed
Status in linux source package in Xenial:
Fix Released
Bug description:
Running the unix_socket_abstract.sh regression test script in a loop
results in an AppArmor WARN message in the logs. On my test system, it
typically takes between 1 and 3 runs of unix_socket_abstract.sh before
the WARN is hit. It does not seem to occur with the
unix_socket_pathname.sh or unix_socket_unnamed.sh tests.
Here's the script I used:
---
#!/bin/sh
dmesg -C
while ! dmesg -c | grep "AppArmor WARN"; do
bash unix_socket_abstract.sh
done
---
The following back trace is emitted in the logs:
[ 1365.017477] ------------[ cut here ]------------
[ 1365.017486] WARNING: CPU: 0 PID: 26026 at /build/buildd/linux-3.16.0/security/apparmor/label.c:1767 __aa_labelset_update_all+0x6f5/0x7f0()
[ 1365.017487] AppArmor WARN __label_update: ((__aa_label_remove_and_insert((&(((label)->ent[(label)->size - 1])->ns)->labels), label, l) != l)):
[ 1365.017489] Modules linked in: bnep rfcomm bluetooth 6lowpan_iphc kvm_intel kvm vmwgfx ttm drm_kms_helper serio_raw drm i2c_piix4 pvpanic parport_pc ppdev mac_hid lp parport psmouse pata_acpi floppy
[ 1365.017505] CPU: 0 PID: 26026 Comm: apparmor_parser Tainted: G W 3.16.0-20-generic #27-Ubuntu
[ 1365.017507] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
[ 1365.017509] 0000000000000009 ffff88002dd23d88 ffffffff8177f053 ffff88002dd23dd0
[ 1365.017511] ffff88002dd23dc0 ffffffff8106fcfd ffff880036602900 0000000000000000
[ 1365.017513] ffff88003acaed00 0000000000000002 ffff88003e02a0a0 ffff88002dd23e20
[ 1365.017516] Call Trace:
[ 1365.017522] [<ffffffff8177f053>] dump_stack+0x45/0x56
[ 1365.017527] [<ffffffff8106fcfd>] warn_slowpath_common+0x7d/0xa0
[ 1365.017530] [<ffffffff8106fd6c>] warn_slowpath_fmt+0x4c/0x50
[ 1365.017533] [<ffffffff8133f00e>] ? __aa_label_remove_and_insert+0x7e/0x1a0
[ 1365.017536] [<ffffffff81342c95>] __aa_labelset_update_all+0x6f5/0x7f0
[ 1365.017539] [<ffffffff812fc5ca>] ? securityfs_remove+0x9a/0xb0
[ 1365.017542] [<ffffffff81338213>] aa_remove_profiles+0x143/0x4f0
[ 1365.017545] [<ffffffff8132f43e>] profile_remove+0x3e/0x70
[ 1365.017550] [<ffffffff811e02c7>] vfs_write+0xb7/0x1f0
[ 1365.017552] [<ffffffff811df439>] ? do_sys_open+0x1b9/0x280
[ 1365.017555] [<ffffffff811e0e76>] SyS_write+0x46/0xb0
[ 1365.017558] [<ffffffff817870ad>] system_call_fastpath+0x1a/0x1f
[ 1365.017560] ---[ end trace 1e09e2c565d9ef95 ]---
This occurs in an amd64 utopic vm:
$ uname -a
Linux sec-utopic-amd64 3.16.0-20-generic #27-Ubuntu SMP Wed Oct 1 17:35:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1378123/+subscriptions
References