[Kernel-packages] [Bug 1378123] Re: unix_socket_abstract.sh triggers an AppArmor WARN

2016-07-07 Thread Dave Chiluk
** Changed in: linux (Ubuntu Wily)
   Status: Confirmed => Won't Fix

** Changed in: linux (Ubuntu Vivid)
   Status: Confirmed => Won't Fix

-- 
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:
  Won't Fix
Status in linux source package in Wily:
  Won't Fix
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: GW
 3.16.0-20-generic #27-Ubuntu
  [ 1365.017507] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
  [ 1365.017509]  0009 88002dd23d88 8177f053 
88002dd23dd0
  [ 1365.017511]  88002dd23dc0 8106fcfd 880036602900 

  [ 1365.017513]  88003acaed00 0002 88003e02a0a0 
88002dd23e20
  [ 1365.017516] Call Trace:
  [ 1365.017522]  [] dump_stack+0x45/0x56
  [ 1365.017527]  [] warn_slowpath_common+0x7d/0xa0
  [ 1365.017530]  [] warn_slowpath_fmt+0x4c/0x50
  [ 1365.017533]  [] ? __aa_label_remove_and_insert+0x7e/0x1a0
  [ 1365.017536]  [] __aa_labelset_update_all+0x6f5/0x7f0
  [ 1365.017539]  [] ? securityfs_remove+0x9a/0xb0
  [ 1365.017542]  [] aa_remove_profiles+0x143/0x4f0
  [ 1365.017545]  [] profile_remove+0x3e/0x70
  [ 1365.017550]  [] vfs_write+0xb7/0x1f0
  [ 1365.017552]  [] ? do_sys_open+0x1b9/0x280
  [ 1365.017555]  [] SyS_write+0x46/0xb0
  [ 1365.017558]  [] 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

-- 
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


[Kernel-packages] [Bug 1378123] Re: unix_socket_abstract.sh triggers an AppArmor WARN

2016-07-07 Thread Dave Chiluk
Thanks guys, I really think the solution here will be to move onto the
lts-xenial kernel as all others lts- kernels will be end of life
shortly.

-- 
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: GW
 3.16.0-20-generic #27-Ubuntu
  [ 1365.017507] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
  [ 1365.017509]  0009 88002dd23d88 8177f053 
88002dd23dd0
  [ 1365.017511]  88002dd23dc0 8106fcfd 880036602900 

  [ 1365.017513]  88003acaed00 0002 88003e02a0a0 
88002dd23e20
  [ 1365.017516] Call Trace:
  [ 1365.017522]  [] dump_stack+0x45/0x56
  [ 1365.017527]  [] warn_slowpath_common+0x7d/0xa0
  [ 1365.017530]  [] warn_slowpath_fmt+0x4c/0x50
  [ 1365.017533]  [] ? __aa_label_remove_and_insert+0x7e/0x1a0
  [ 1365.017536]  [] __aa_labelset_update_all+0x6f5/0x7f0
  [ 1365.017539]  [] ? securityfs_remove+0x9a/0xb0
  [ 1365.017542]  [] aa_remove_profiles+0x143/0x4f0
  [ 1365.017545]  [] profile_remove+0x3e/0x70
  [ 1365.017550]  [] vfs_write+0xb7/0x1f0
  [ 1365.017552]  [] ? do_sys_open+0x1b9/0x280
  [ 1365.017555]  [] SyS_write+0x46/0xb0
  [ 1365.017558]  [] 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

-- 
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


[Kernel-packages] [Bug 1378123] Re: unix_socket_abstract.sh triggers an AppArmor WARN

2016-07-01 Thread John Johansen
This should be fixed in Xenial, there is a large patchset (30 or so
patches) that can be SRUed to vivids 3.16 kernel

-- 
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: GW
 3.16.0-20-generic #27-Ubuntu
  [ 1365.017507] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
  [ 1365.017509]  0009 88002dd23d88 8177f053 
88002dd23dd0
  [ 1365.017511]  88002dd23dc0 8106fcfd 880036602900 

  [ 1365.017513]  88003acaed00 0002 88003e02a0a0 
88002dd23e20
  [ 1365.017516] Call Trace:
  [ 1365.017522]  [] dump_stack+0x45/0x56
  [ 1365.017527]  [] warn_slowpath_common+0x7d/0xa0
  [ 1365.017530]  [] warn_slowpath_fmt+0x4c/0x50
  [ 1365.017533]  [] ? __aa_label_remove_and_insert+0x7e/0x1a0
  [ 1365.017536]  [] __aa_labelset_update_all+0x6f5/0x7f0
  [ 1365.017539]  [] ? securityfs_remove+0x9a/0xb0
  [ 1365.017542]  [] aa_remove_profiles+0x143/0x4f0
  [ 1365.017545]  [] profile_remove+0x3e/0x70
  [ 1365.017550]  [] vfs_write+0xb7/0x1f0
  [ 1365.017552]  [] ? do_sys_open+0x1b9/0x280
  [ 1365.017555]  [] SyS_write+0x46/0xb0
  [ 1365.017558]  [] 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

-- 
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


[Kernel-packages] [Bug 1378123] Re: unix_socket_abstract.sh triggers an AppArmor WARN

2016-07-01 Thread Tyler Hicks
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: GW
 3.16.0-20-generic #27-Ubuntu
  [ 1365.017507] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
  [ 1365.017509]  0009 88002dd23d88 8177f053 
88002dd23dd0
  [ 1365.017511]  88002dd23dc0 8106fcfd 880036602900 

  [ 1365.017513]  88003acaed00 0002 88003e02a0a0 
88002dd23e20
  [ 1365.017516] Call Trace:
  [ 1365.017522]  [] dump_stack+0x45/0x56
  [ 1365.017527]  [] warn_slowpath_common+0x7d/0xa0
  [ 1365.017530]  [] warn_slowpath_fmt+0x4c/0x50
  [ 1365.017533]  [] ? __aa_label_remove_and_insert+0x7e/0x1a0
  [ 1365.017536]  [] __aa_labelset_update_all+0x6f5/0x7f0
  [ 1365.017539]  [] ? securityfs_remove+0x9a/0xb0
  [ 1365.017542]  [] aa_remove_profiles+0x143/0x4f0
  [ 1365.017545]  [] profile_remove+0x3e/0x70
  [ 1365.017550]  [] vfs_write+0xb7/0x1f0
  [ 1365.017552]  [] ? do_sys_open+0x1b9/0x280
  [ 1365.017555]  [] SyS_write+0x46/0xb0
  [ 1365.017558]  [] 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

-- 
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


[Kernel-packages] [Bug 1378123] Re: unix_socket_abstract.sh triggers an AppArmor WARN

2016-07-01 Thread Tyler Hicks
I was able to hit this in 14.04 with linux-generic-lts-wily installed:

  $ cat /proc/version_signature 
  Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11

The 14.04 apparmor_parser doesn't support unix rules, so you need to
check out lp:apparmor, build libapparmor and the parser and the
unix_socket regression tests before using the reproducer in the bug
description.

-- 
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:
  Confirmed

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: GW
 3.16.0-20-generic #27-Ubuntu
  [ 1365.017507] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
  [ 1365.017509]  0009 88002dd23d88 8177f053 
88002dd23dd0
  [ 1365.017511]  88002dd23dc0 8106fcfd 880036602900 

  [ 1365.017513]  88003acaed00 0002 88003e02a0a0 
88002dd23e20
  [ 1365.017516] Call Trace:
  [ 1365.017522]  [] dump_stack+0x45/0x56
  [ 1365.017527]  [] warn_slowpath_common+0x7d/0xa0
  [ 1365.017530]  [] warn_slowpath_fmt+0x4c/0x50
  [ 1365.017533]  [] ? __aa_label_remove_and_insert+0x7e/0x1a0
  [ 1365.017536]  [] __aa_labelset_update_all+0x6f5/0x7f0
  [ 1365.017539]  [] ? securityfs_remove+0x9a/0xb0
  [ 1365.017542]  [] aa_remove_profiles+0x143/0x4f0
  [ 1365.017545]  [] profile_remove+0x3e/0x70
  [ 1365.017550]  [] vfs_write+0xb7/0x1f0
  [ 1365.017552]  [] ? do_sys_open+0x1b9/0x280
  [ 1365.017555]  [] SyS_write+0x46/0xb0
  [ 1365.017558]  [] 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

-- 
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


[Kernel-packages] [Bug 1378123] Re: unix_socket_abstract.sh triggers an AppArmor WARN

2016-07-01 Thread Tyler Hicks
I can't reproduce this issue on Xenial (4.4.0-28.47-generic). It may be
fixed there or maybe I'm just not winning the race (condition).

-- 
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:
  Confirmed

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: GW
 3.16.0-20-generic #27-Ubuntu
  [ 1365.017507] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
  [ 1365.017509]  0009 88002dd23d88 8177f053 
88002dd23dd0
  [ 1365.017511]  88002dd23dc0 8106fcfd 880036602900 

  [ 1365.017513]  88003acaed00 0002 88003e02a0a0 
88002dd23e20
  [ 1365.017516] Call Trace:
  [ 1365.017522]  [] dump_stack+0x45/0x56
  [ 1365.017527]  [] warn_slowpath_common+0x7d/0xa0
  [ 1365.017530]  [] warn_slowpath_fmt+0x4c/0x50
  [ 1365.017533]  [] ? __aa_label_remove_and_insert+0x7e/0x1a0
  [ 1365.017536]  [] __aa_labelset_update_all+0x6f5/0x7f0
  [ 1365.017539]  [] ? securityfs_remove+0x9a/0xb0
  [ 1365.017542]  [] aa_remove_profiles+0x143/0x4f0
  [ 1365.017545]  [] profile_remove+0x3e/0x70
  [ 1365.017550]  [] vfs_write+0xb7/0x1f0
  [ 1365.017552]  [] ? do_sys_open+0x1b9/0x280
  [ 1365.017555]  [] SyS_write+0x46/0xb0
  [ 1365.017558]  [] 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

-- 
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


[Kernel-packages] [Bug 1378123] Re: unix_socket_abstract.sh triggers an AppArmor WARN

2016-07-01 Thread Dave Chiluk
** Tags added: sts

-- 
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:
  Confirmed

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: GW
 3.16.0-20-generic #27-Ubuntu
  [ 1365.017507] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
  [ 1365.017509]  0009 88002dd23d88 8177f053 
88002dd23dd0
  [ 1365.017511]  88002dd23dc0 8106fcfd 880036602900 

  [ 1365.017513]  88003acaed00 0002 88003e02a0a0 
88002dd23e20
  [ 1365.017516] Call Trace:
  [ 1365.017522]  [] dump_stack+0x45/0x56
  [ 1365.017527]  [] warn_slowpath_common+0x7d/0xa0
  [ 1365.017530]  [] warn_slowpath_fmt+0x4c/0x50
  [ 1365.017533]  [] ? __aa_label_remove_and_insert+0x7e/0x1a0
  [ 1365.017536]  [] __aa_labelset_update_all+0x6f5/0x7f0
  [ 1365.017539]  [] ? securityfs_remove+0x9a/0xb0
  [ 1365.017542]  [] aa_remove_profiles+0x143/0x4f0
  [ 1365.017545]  [] profile_remove+0x3e/0x70
  [ 1365.017550]  [] vfs_write+0xb7/0x1f0
  [ 1365.017552]  [] ? do_sys_open+0x1b9/0x280
  [ 1365.017555]  [] SyS_write+0x46/0xb0
  [ 1365.017558]  [] 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

-- 
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


[Kernel-packages] [Bug 1378123] Re: unix_socket_abstract.sh triggers an AppArmor WARN

2015-05-26 Thread Tyler Hicks
** Tags added: aa-kernel

-- 
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:
  Confirmed

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: GW
 3.16.0-20-generic #27-Ubuntu
  [ 1365.017507] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
  [ 1365.017509]  0009 88002dd23d88 8177f053 
88002dd23dd0
  [ 1365.017511]  88002dd23dc0 8106fcfd 880036602900 

  [ 1365.017513]  88003acaed00 0002 88003e02a0a0 
88002dd23e20
  [ 1365.017516] Call Trace:
  [ 1365.017522]  [8177f053] dump_stack+0x45/0x56
  [ 1365.017527]  [8106fcfd] warn_slowpath_common+0x7d/0xa0
  [ 1365.017530]  [8106fd6c] warn_slowpath_fmt+0x4c/0x50
  [ 1365.017533]  [8133f00e] ? __aa_label_remove_and_insert+0x7e/0x1a0
  [ 1365.017536]  [81342c95] __aa_labelset_update_all+0x6f5/0x7f0
  [ 1365.017539]  [812fc5ca] ? securityfs_remove+0x9a/0xb0
  [ 1365.017542]  [81338213] aa_remove_profiles+0x143/0x4f0
  [ 1365.017545]  [8132f43e] profile_remove+0x3e/0x70
  [ 1365.017550]  [811e02c7] vfs_write+0xb7/0x1f0
  [ 1365.017552]  [811df439] ? do_sys_open+0x1b9/0x280
  [ 1365.017555]  [811e0e76] SyS_write+0x46/0xb0
  [ 1365.017558]  [817870ad] 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

-- 
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


[Kernel-packages] [Bug 1378123] Re: unix_socket_abstract.sh triggers an AppArmor WARN

2015-05-25 Thread Laurent Salle
The AppArmor WARN __label_update warnings are occuring on a production
system:

$ uname -a
Linux svbom 3.19.0-18-generic #18-Ubuntu SMP Tue May 19 18:31:35 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=15.04
DISTRIB_CODENAME=vivid
DISTRIB_DESCRIPTION=Ubuntu 15.04

Two dmesg excerpts:

--
[56434.648170] br3: port 6(vnet18) entered disabled state
[56434.648212] device vnet18 left promiscuous mode
[56434.648215] br3: port 6(vnet18) entered disabled state
[56435.050149] [ cut here ]
[56435.050155] WARNING: CPU: 6 PID: 24903 at 
/build/buildd/linux-3.19.0/security/apparmor/label.c:1767 
__aa_labelset_update_all+0x710/0x800()
[56435.050156] AppArmor WARN __label_update: 
((__aa_label_remove_and_insert(label)-ent[(label)-size - 
1])-ns)-labels), label, l) != l)): 
[56435.050157] Modules linked in:
[56435.050159]  joydev hid_generic usbhid hid vhost_net vhost macvtap macvlan 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables 
x_tables bridge stp llc intel_rapl iosf_mbi x86_pkg_temp_thermal ipmi_ssif 
intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel hpilo lpc_ich aes_x86_64 lrw ie31200_edac 
gf128mul shpchp glue_helper 8250_fintek ipmi_si ablk_helper edac_core 
ipmi_msghandler cryptd mac_hid acpi_power_meter serio_raw lp parport autofs4 
tg3 ahci ptp psmouse libahci pps_core hpsa
[56435.050182] CPU: 6 PID: 24903 Comm: apparmor_parser Tainted: GW  
3.19.0-18-generic #18-Ubuntu
[56435.050183] Hardware name: HP ProLiant DL320e Gen8 v2, BIOS P80 09/01/2013
[56435.050184]  81ad2178 8806d006bd38 817c27cd 
0007
[56435.050186]  8806d006bd88 8806d006bd78 8107593a 
8806f4267408
[56435.050187]  88060a74dd00  8806b55f6e00 
0002
[56435.050188] Call Trace:
[56435.050192]  [817c27cd] dump_stack+0x45/0x57
[56435.050195]  [8107593a] warn_slowpath_common+0x8a/0xc0
[56435.050196]  [810759b6] warn_slowpath_fmt+0x46/0x50
[56435.050199]  [81358b65] ? __aa_label_remove_and_insert+0x85/0x1a0
[56435.050200]  [8135c8f0] __aa_labelset_update_all+0x710/0x800
[56435.050203]  [8131518a] ? securityfs_remove+0x9a/0xb0
[56435.050205]  [81351bf8] aa_remove_profiles+0x148/0x500
[56435.050206]  [81348b1a] ? aa_simple_write_to_buffer+0x7a/0xa0
[56435.050208]  [81348b7e] profile_remove+0x3e/0x70
[56435.050210]  [811f38a7] vfs_write+0xb7/0x1f0
[56435.050212]  [811f2a29] ? do_sys_open+0x1b9/0x280
[56435.050214]  [811f44b6] SyS_write+0x46/0xb0
[56435.050216]  [817c990d] system_call_fastpath+0x16/0x1b
[56435.050217] ---[ end trace 00bcc1692506d99a ]---
--

--
[61376.416886] br3: port 7(vnet20) entered disabled state
[61376.416934] device vnet20 left promiscuous mode
[61376.416937] br3: port 7(vnet20) entered disabled state
[61376.706953] [ cut here ]
[61376.706969] WARNING: CPU: 3 PID: 33012 at 
/build/buildd/linux-3.19.0/security/apparmor/label.c:1767 
__aa_labelset_update_all+0x710/0x800()
[61376.706970] AppArmor WARN __label_update: 
((__aa_label_remove_and_insert(label)-ent[(label)-size - 
1])-ns)-labels), label, l) != l)): 
[61376.706971] Modules linked in:
[61376.706972]  joydev hid_generic usbhid hid vhost_net vhost macvtap macvlan 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables 
x_tables bridge stp llc intel_rapl iosf_mbi x86_pkg_temp_thermal ipmi_ssif 
intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel hpilo lpc_ich aes_x86_64 lrw ie31200_edac 
gf128mul shpchp glue_helper 8250_fintek ipmi_si ablk_helper edac_core 
ipmi_msghandler cryptd mac_hid acpi_power_meter serio_raw lp parport autofs4 
tg3 ahci ptp psmouse libahci pps_core hpsa
[61376.706995] CPU: 3 PID: 33012 Comm: apparmor_parser Tainted: GW  
3.19.0-18-generic #18-Ubuntu
[61376.706996] Hardware name: HP ProLiant DL320e Gen8 v2, BIOS P80 09/01/2013
[61376.706997]  81ad2178 88052380fd38 817c27cd 
0007
[61376.706998]  88052380fd88 88052380fd78 8107593a 
8806f4267408
[61376.706999]  880609de6300  88060a6ce800 
0002
[61376.707001] Call Trace:
[61376.707005]  [817c27cd] dump_stack+0x45/0x57
[61376.707007]  [8107593a] warn_slowpath_common+0x8a/0xc0
[61376.707009]  [810759b6] warn_slowpath_fmt+0x46/0x50
[61376.707012]  [81358b65] ? __aa_label_remove_and_insert+0x85/0x1a0
[61376.707013]  [8135c8f0] __aa_labelset_update_all+0x710/0x800
[61376.707015]  [8131518a] ? securityfs_remove+0x9a/0xb0
[61376.707017]  [81351bf8] aa_remove_profiles+0x148/0x500
[61376.707019]  [81348b1a] ? aa_simple_write_to_buffer+0x7a/0xa0
[61376.707020]  [81348b7e] profile_remove+0x3e/0x70

[Kernel-packages] [Bug 1378123] Re: unix_socket_abstract.sh triggers an AppArmor WARN

2014-10-07 Thread Tyler Hicks
** Description changed:

  Running the unix_socket_abstract.sh regression test script in a loop
- results in an AppArmor WARN message in the logs.
+ 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
+ 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: GW
 3.16.0-20-generic #27-Ubuntu
- [ 1365.017507] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011 
+ [ 1365.017507] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
  [ 1365.017509]  0009 88002dd23d88 8177f053 
88002dd23dd0
  [ 1365.017511]  88002dd23dc0 8106fcfd 880036602900 

  [ 1365.017513]  88003acaed00 0002 88003e02a0a0 
88002dd23e20
  [ 1365.017516] Call Trace:
  [ 1365.017522]  [8177f053] dump_stack+0x45/0x56
  [ 1365.017527]  [8106fcfd] warn_slowpath_common+0x7d/0xa0
  [ 1365.017530]  [8106fd6c] warn_slowpath_fmt+0x4c/0x50
  [ 1365.017533]  [8133f00e] ? __aa_label_remove_and_insert+0x7e/0x1a0
  [ 1365.017536]  [81342c95] __aa_labelset_update_all+0x6f5/0x7f0
  [ 1365.017539]  [812fc5ca] ? securityfs_remove+0x9a/0xb0
  [ 1365.017542]  [81338213] aa_remove_profiles+0x143/0x4f0
  [ 1365.017545]  [8132f43e] profile_remove+0x3e/0x70
  [ 1365.017550]  [811e02c7] vfs_write+0xb7/0x1f0
  [ 1365.017552]  [811df439] ? do_sys_open+0x1b9/0x280
- [ 1365.017555]  [811e0e76] SyS_write+0x46/0xb0 
+ [ 1365.017555]  [811e0e76] SyS_write+0x46/0xb0
  [ 1365.017558]  [817870ad] 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

-- 
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:
  Confirmed

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: GW
 3.16.0-20-generic #27-Ubuntu
  [ 1365.017507] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
  [ 1365.017509]  0009 88002dd23d88 8177f053 
88002dd23dd0
  [ 1365.017511]  88002dd23dc0 8106fcfd 880036602900 

  [ 1365.017513]  88003acaed00 0002 88003e02a0a0 
88002dd23e20
  [ 1365.017516] Call Trace:
  [ 1365.017522]  [8177f053] dump_stack+0x45/0x56
  [ 1365.017527]  [8106fcfd] warn_slowpath_common+0x7d/0xa0
  [ 1365.017530]  [8106fd6c] warn_slowpath_fmt+0x4c/0x50
  [ 1365.017533]  [8133f00e] ?