Creating a new namespace results in an AppArmor WARN
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
AppArmor |
Triaged
|
High
|
John Johansen |
Bug Description
Aftering creating a new namespace with the following command:
$ echo ":namespace:p {}" | sudo apparmor_parser -qr
Check the syslog for an AppArmor WARN:
------------[ cut here ]------------
WARNING: CPU: 0 PID: 2055 at /build/
AppArmor WARN __aa_fs_
Modules linked in:
kvm_intel kvm crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd input_leds joydev serio_raw i2c_piix4 8250_fintek mac_hid parport_pc ppdev lp parport autofs4 vmwgfx ttm drm_kms_helper psmouse drm floppy pata_acpi
CPU: 0 PID: 2055 Comm: apparmor_parser Tainted: G W 4.2.0-27-generic #32-Ubuntu
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-
0000000000000000 000000004aa409a6 ffff88003bbdfcc8 ffffffff817eae99
0000000000000000 ffff88003bbdfd20 ffff88003bbdfd08 ffffffff8107b9c6
ffff8800397c52c4 ffff88003978a820 ffff88003d4f6e40 ffff88003a93ac00
Call Trace:
[<ffffffff817e
[<ffffffff8107
[<ffffffff8107
[<ffffffff8136
[<ffffffff8135
[<ffffffff8136
[<ffffffff8132
[<ffffffff811d
[<ffffffff8136
[<ffffffff8135
[<ffffffff811f
[<ffffffff811f
[<ffffffff811f
[<ffffffff811f
[<ffffffff817f
---[ end trace eb040f6cc3cf8ca3 ]---
$ uname -a
Linux sec-wily-amd64 4.2.0-27-generic #32-Ubuntu SMP Fri Jan 22 04:49:08 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
tags: | added: aa-kernel |
Assigning this to John since he is fixing this for Xenial.