[Kernel-packages] [Bug 1235977] Re: apparmor bad lock balance during policy introspection
This bug was fixed in the package linux-manta - 3.4.0-4.19
---
linux-manta (3.4.0-4.19) saucy; urgency=low
[ John Johansen ]
* SAUCE: apparmor: fix unix domain sockets to be mediated on connection
- LP: #1208988
* SAUCE: apparmor: allocate path lookup buffers during init
- LP: #1208988
* SAUCE: apparmor: fix memleak of the profile hash
- LP: #1235523
* SAUCE: apparmor: fix memleak of replacedby struct
- LP: #1235973
* SAUCE: apparmor: fix bad lock balance when introspecting policy
- LP: #1235977
[ Scott James Remnant ]
* SAUCE: (no-up) trace: add trace events for open(), exec() and uselib()
- LP: #1194127
-- Andy WhitcroftMon, 07 Oct 2013 18:23:03 +0100
** Changed in: linux-manta (Ubuntu Saucy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-maguro in Ubuntu.
https://bugs.launchpad.net/bugs/1235977
Title:
apparmor bad lock balance during policy introspection
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux-goldfish” package in Ubuntu:
Fix Released
Status in “linux-grouper” package in Ubuntu:
Fix Released
Status in “linux-maguro” package in Ubuntu:
Fix Released
Status in “linux-mako” package in Ubuntu:
Fix Released
Status in “linux-manta” package in Ubuntu:
Fix Released
Status in “linux” source package in Saucy:
Fix Released
Status in “linux-goldfish” source package in Saucy:
Fix Released
Status in “linux-grouper” source package in Saucy:
Fix Released
Status in “linux-maguro” source package in Saucy:
Fix Released
Status in “linux-mako” source package in Saucy:
Fix Released
Status in “linux-manta” source package in Saucy:
Fix Released
Bug description:
There is a bug in the profile introspection file that results in a
virtual root ns lock being released twice. Introspection from the root
policy namespace is handled correctly it is only when introspection is
done from a task in a sub policy namespace that becomes its virtual ns
root.
This results in the following lockdep trace
[ 78.479744] [ BUG: bad unlock balance detected! ]
[ 78.479792] 3.11.0-11-generic #17 Not tainted
[ 78.479838] -
[ 78.479885] grep/2223 is trying to release lock (&ns->lock) at:
[ 78.479952] [] mutex_unlock+0xe/0x10
[ 78.480002] but there are no more locks to release!
[ 78.480037]
[ 78.480037] other info that might help us debug this:
[ 78.480037] 1 lock held by grep/2223:
[ 78.480037] #0: (&p->lock){+.+.+.}, at: []
seq_read+0x3d/0x3d0
[ 78.480037]
[ 78.480037] stack backtrace:
[ 78.480037] CPU: 0 PID: 2223 Comm: grep Not tainted 3.11.0-11-generic #17
[ 78.480037] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[ 78.480037] 817bf3be 880007763d60 817b97ef
8800189d2190
[ 78.480037] 880007763d88 810e1c6e 88001f044730
8800189d2190
[ 78.480037] 817bf3be 880007763e00 810e5bd6
000724fe56b7
[ 78.480037] Call Trace:
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] dump_stack+0x54/0x74
[ 78.480037] [] print_unlock_imbalance_bug+0xee/0x100
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] lock_release_non_nested+0x226/0x300
[ 78.480037] [] ? __mutex_unlock_slowpath+0xce/0x180
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] lock_release+0xac/0x310
[ 78.480037] [] __mutex_unlock_slowpath+0x83/0x180
[ 78.480037] [] mutex_unlock+0xe/0x10
[ 78.480037] [] p_stop+0x51/0x90
[ 78.480037] [] seq_read+0x288/0x3d0
[ 78.480037] [] vfs_read+0x9e/0x170
[ 78.480037] [] SyS_read+0x4c/0xa0
[ 78.480037] [] system_call_fastpath+0x1a/0x1f
Requires:
user of policy namespaces
root process with in alternate policy namespace reading the
/sys/kernel/security/apparmor/profiles file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235977/+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 1235977] Re: apparmor bad lock balance during policy introspection
This bug was fixed in the package linux-maguro - 3.0.0-3.18
---
linux-maguro (3.0.0-3.18) saucy; urgency=low
[ John Johansen ]
* SAUCE: apparmor: fix unix domain sockets to be mediated on connection
- LP: #1208988
* SAUCE: apparmor: allocate path lookup buffers during init
- LP: #1208988
* SAUCE: apparmor: fix memleak of the profile hash
- LP: #1235523
* SAUCE: apparmor: fix memleak of replacedby struct
- LP: #1235973
* SAUCE: apparmor: fix bad lock balance when introspecting policy
- LP: #1235977
-- Andy WhitcroftMon, 07 Oct 2013 17:16:14 +0100
** Changed in: linux-mako (Ubuntu Saucy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-maguro in Ubuntu.
https://bugs.launchpad.net/bugs/1235977
Title:
apparmor bad lock balance during policy introspection
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux-goldfish” package in Ubuntu:
Fix Released
Status in “linux-grouper” package in Ubuntu:
Fix Released
Status in “linux-maguro” package in Ubuntu:
Fix Released
Status in “linux-mako” package in Ubuntu:
Fix Released
Status in “linux-manta” package in Ubuntu:
Fix Committed
Status in “linux” source package in Saucy:
Fix Released
Status in “linux-goldfish” source package in Saucy:
Fix Released
Status in “linux-grouper” source package in Saucy:
Fix Released
Status in “linux-maguro” source package in Saucy:
Fix Released
Status in “linux-mako” source package in Saucy:
Fix Released
Status in “linux-manta” source package in Saucy:
Fix Committed
Bug description:
There is a bug in the profile introspection file that results in a
virtual root ns lock being released twice. Introspection from the root
policy namespace is handled correctly it is only when introspection is
done from a task in a sub policy namespace that becomes its virtual ns
root.
This results in the following lockdep trace
[ 78.479744] [ BUG: bad unlock balance detected! ]
[ 78.479792] 3.11.0-11-generic #17 Not tainted
[ 78.479838] -
[ 78.479885] grep/2223 is trying to release lock (&ns->lock) at:
[ 78.479952] [] mutex_unlock+0xe/0x10
[ 78.480002] but there are no more locks to release!
[ 78.480037]
[ 78.480037] other info that might help us debug this:
[ 78.480037] 1 lock held by grep/2223:
[ 78.480037] #0: (&p->lock){+.+.+.}, at: []
seq_read+0x3d/0x3d0
[ 78.480037]
[ 78.480037] stack backtrace:
[ 78.480037] CPU: 0 PID: 2223 Comm: grep Not tainted 3.11.0-11-generic #17
[ 78.480037] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[ 78.480037] 817bf3be 880007763d60 817b97ef
8800189d2190
[ 78.480037] 880007763d88 810e1c6e 88001f044730
8800189d2190
[ 78.480037] 817bf3be 880007763e00 810e5bd6
000724fe56b7
[ 78.480037] Call Trace:
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] dump_stack+0x54/0x74
[ 78.480037] [] print_unlock_imbalance_bug+0xee/0x100
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] lock_release_non_nested+0x226/0x300
[ 78.480037] [] ? __mutex_unlock_slowpath+0xce/0x180
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] lock_release+0xac/0x310
[ 78.480037] [] __mutex_unlock_slowpath+0x83/0x180
[ 78.480037] [] mutex_unlock+0xe/0x10
[ 78.480037] [] p_stop+0x51/0x90
[ 78.480037] [] seq_read+0x288/0x3d0
[ 78.480037] [] vfs_read+0x9e/0x170
[ 78.480037] [] SyS_read+0x4c/0xa0
[ 78.480037] [] system_call_fastpath+0x1a/0x1f
Requires:
user of policy namespaces
root process with in alternate policy namespace reading the
/sys/kernel/security/apparmor/profiles file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235977/+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 1235977] Re: apparmor bad lock balance during policy introspection
This bug was fixed in the package linux-mako - 3.4.0-3.21
---
linux-mako (3.4.0-3.21) saucy; urgency=low
[ John Johansen ]
* SAUCE: apparmor: fix unix domain sockets to be mediated on connection
- LP: #1208988
* SAUCE: apparmor: allocate path lookup buffers during init
- LP: #1208988
* SAUCE: apparmor: fix memleak of the profile hash
- LP: #1235523
* SAUCE: apparmor: fix memleak of replacedby struct
- LP: #1235973
* SAUCE: apparmor: fix bad lock balance when introspecting policy
- LP: #1235977
[ Scott James Remnant ]
* SAUCE: (no-up) trace: add trace events for open(), exec() and uselib()
- LP: #1194127
-- Andy WhitcroftMon, 07 Oct 2013 18:17:50 +0100
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-maguro in Ubuntu.
https://bugs.launchpad.net/bugs/1235977
Title:
apparmor bad lock balance during policy introspection
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux-goldfish” package in Ubuntu:
Fix Released
Status in “linux-grouper” package in Ubuntu:
Fix Released
Status in “linux-maguro” package in Ubuntu:
Fix Released
Status in “linux-mako” package in Ubuntu:
Fix Released
Status in “linux-manta” package in Ubuntu:
Fix Committed
Status in “linux” source package in Saucy:
Fix Released
Status in “linux-goldfish” source package in Saucy:
Fix Released
Status in “linux-grouper” source package in Saucy:
Fix Released
Status in “linux-maguro” source package in Saucy:
Fix Released
Status in “linux-mako” source package in Saucy:
Fix Released
Status in “linux-manta” source package in Saucy:
Fix Committed
Bug description:
There is a bug in the profile introspection file that results in a
virtual root ns lock being released twice. Introspection from the root
policy namespace is handled correctly it is only when introspection is
done from a task in a sub policy namespace that becomes its virtual ns
root.
This results in the following lockdep trace
[ 78.479744] [ BUG: bad unlock balance detected! ]
[ 78.479792] 3.11.0-11-generic #17 Not tainted
[ 78.479838] -
[ 78.479885] grep/2223 is trying to release lock (&ns->lock) at:
[ 78.479952] [] mutex_unlock+0xe/0x10
[ 78.480002] but there are no more locks to release!
[ 78.480037]
[ 78.480037] other info that might help us debug this:
[ 78.480037] 1 lock held by grep/2223:
[ 78.480037] #0: (&p->lock){+.+.+.}, at: []
seq_read+0x3d/0x3d0
[ 78.480037]
[ 78.480037] stack backtrace:
[ 78.480037] CPU: 0 PID: 2223 Comm: grep Not tainted 3.11.0-11-generic #17
[ 78.480037] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[ 78.480037] 817bf3be 880007763d60 817b97ef
8800189d2190
[ 78.480037] 880007763d88 810e1c6e 88001f044730
8800189d2190
[ 78.480037] 817bf3be 880007763e00 810e5bd6
000724fe56b7
[ 78.480037] Call Trace:
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] dump_stack+0x54/0x74
[ 78.480037] [] print_unlock_imbalance_bug+0xee/0x100
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] lock_release_non_nested+0x226/0x300
[ 78.480037] [] ? __mutex_unlock_slowpath+0xce/0x180
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] lock_release+0xac/0x310
[ 78.480037] [] __mutex_unlock_slowpath+0x83/0x180
[ 78.480037] [] mutex_unlock+0xe/0x10
[ 78.480037] [] p_stop+0x51/0x90
[ 78.480037] [] seq_read+0x288/0x3d0
[ 78.480037] [] vfs_read+0x9e/0x170
[ 78.480037] [] SyS_read+0x4c/0xa0
[ 78.480037] [] system_call_fastpath+0x1a/0x1f
Requires:
user of policy namespaces
root process with in alternate policy namespace reading the
/sys/kernel/security/apparmor/profiles file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235977/+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 1235977] Re: apparmor bad lock balance during policy introspection
This bug was fixed in the package linux-grouper - 3.1.10-6.25
---
linux-grouper (3.1.10-6.25) saucy; urgency=low
[ John Johansen ]
* SAUCE: apparmor: fix unix domain sockets to be mediated on connection
- LP: #1208988
* SAUCE: apparmor: allocate path lookup buffers during init
- LP: #1208988
* SAUCE: apparmor: fix memleak of the profile hash
- LP: #1235523
* SAUCE: apparmor: fix memleak of replacedby struct
- LP: #1235973
* SAUCE: apparmor: fix bad lock balance when introspecting policy
- LP: #1235977
-- Andy WhitcroftMon, 07 Oct 2013 16:50:39 +0100
** Changed in: linux-grouper (Ubuntu Saucy)
Status: Fix Committed => Fix Released
** Changed in: linux-maguro (Ubuntu Saucy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-maguro in Ubuntu.
https://bugs.launchpad.net/bugs/1235977
Title:
apparmor bad lock balance during policy introspection
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux-goldfish” package in Ubuntu:
Fix Released
Status in “linux-grouper” package in Ubuntu:
Fix Released
Status in “linux-maguro” package in Ubuntu:
Fix Released
Status in “linux-mako” package in Ubuntu:
Fix Released
Status in “linux-manta” package in Ubuntu:
Fix Committed
Status in “linux” source package in Saucy:
Fix Released
Status in “linux-goldfish” source package in Saucy:
Fix Released
Status in “linux-grouper” source package in Saucy:
Fix Released
Status in “linux-maguro” source package in Saucy:
Fix Released
Status in “linux-mako” source package in Saucy:
Fix Released
Status in “linux-manta” source package in Saucy:
Fix Committed
Bug description:
There is a bug in the profile introspection file that results in a
virtual root ns lock being released twice. Introspection from the root
policy namespace is handled correctly it is only when introspection is
done from a task in a sub policy namespace that becomes its virtual ns
root.
This results in the following lockdep trace
[ 78.479744] [ BUG: bad unlock balance detected! ]
[ 78.479792] 3.11.0-11-generic #17 Not tainted
[ 78.479838] -
[ 78.479885] grep/2223 is trying to release lock (&ns->lock) at:
[ 78.479952] [] mutex_unlock+0xe/0x10
[ 78.480002] but there are no more locks to release!
[ 78.480037]
[ 78.480037] other info that might help us debug this:
[ 78.480037] 1 lock held by grep/2223:
[ 78.480037] #0: (&p->lock){+.+.+.}, at: []
seq_read+0x3d/0x3d0
[ 78.480037]
[ 78.480037] stack backtrace:
[ 78.480037] CPU: 0 PID: 2223 Comm: grep Not tainted 3.11.0-11-generic #17
[ 78.480037] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[ 78.480037] 817bf3be 880007763d60 817b97ef
8800189d2190
[ 78.480037] 880007763d88 810e1c6e 88001f044730
8800189d2190
[ 78.480037] 817bf3be 880007763e00 810e5bd6
000724fe56b7
[ 78.480037] Call Trace:
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] dump_stack+0x54/0x74
[ 78.480037] [] print_unlock_imbalance_bug+0xee/0x100
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] lock_release_non_nested+0x226/0x300
[ 78.480037] [] ? __mutex_unlock_slowpath+0xce/0x180
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] lock_release+0xac/0x310
[ 78.480037] [] __mutex_unlock_slowpath+0x83/0x180
[ 78.480037] [] mutex_unlock+0xe/0x10
[ 78.480037] [] p_stop+0x51/0x90
[ 78.480037] [] seq_read+0x288/0x3d0
[ 78.480037] [] vfs_read+0x9e/0x170
[ 78.480037] [] SyS_read+0x4c/0xa0
[ 78.480037] [] system_call_fastpath+0x1a/0x1f
Requires:
user of policy namespaces
root process with in alternate policy namespace reading the
/sys/kernel/security/apparmor/profiles file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235977/+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 1235977] Re: apparmor bad lock balance during policy introspection
This bug was fixed in the package linux - 3.11.0-12.18
---
linux (3.11.0-12.18) saucy; urgency=low
[ Andy Whitcroft ]
* [Packing] tools -- when tools are off they are off
* [config] tools -- linux-tools-common really is common
* [Packaging] tools -- make cpupower optional
* [Packaging] tools -- fix crosscompilation
* [config] tools -- enable cpupower
* SAUCE: storvsc -- host takes MAINTENANCE_IN commands badly elide them
- LP: #1234417
[ John Johansen ]
* SAUCE: apparmor: fix unix domain sockets to be mediated on connection
- LP: #1208988
* SAUCE: apparmor: allocate path lookup buffers during init
- LP: #1208988
* SAUCE: apparmor: fix memleak of the profile hash
- LP: #1235523
* SAUCE: apparmor: fix memleak of replacedby struct
- LP: #1235973
* SAUCE: apparmor: fix bad lock balance when introspecting policy
- LP: #1235977
[ Paolo Pisati ]
* [Config] arm: VIRTIO_[BLK|NET|MMIO]=y
[ Rob Herring ]
* SAUCE: (no-up) net: calxedaxgmac: fix clearing of old filter addresses
- LP: #1235272
* SAUCE: (no-up) net: calxedaxgmac: add uc and mc filter addresses in
promiscuous mode
- LP: #1235272
* SAUCE: (no-up) net: calxedaxgmac: determine number of address filters
at runtime
- LP: #1235272
[ Tim Gardner ]
* [Config] CONFIG_ANDROID=n
- LP: #1235161
* [Config] CONFIG_L2TP_V3=y
- LP: #1235914
* Release tracker
- LP: #1236999
[ Upstream Kernel Changes ]
* Revert "HID: core: fix reporting of raw events"
- LP: #1218004
-- Andy WhitcroftFri, 04 Oct 2013 13:08:59 +0100
** Changed in: linux (Ubuntu Saucy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-maguro in Ubuntu.
https://bugs.launchpad.net/bugs/1235977
Title:
apparmor bad lock balance during policy introspection
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux-goldfish” package in Ubuntu:
Fix Released
Status in “linux-grouper” package in Ubuntu:
Fix Committed
Status in “linux-maguro” package in Ubuntu:
Fix Committed
Status in “linux-mako” package in Ubuntu:
Fix Committed
Status in “linux-manta” package in Ubuntu:
Fix Committed
Status in “linux” source package in Saucy:
Fix Released
Status in “linux-goldfish” source package in Saucy:
Fix Released
Status in “linux-grouper” source package in Saucy:
Fix Committed
Status in “linux-maguro” source package in Saucy:
Fix Committed
Status in “linux-mako” source package in Saucy:
Fix Committed
Status in “linux-manta” source package in Saucy:
Fix Committed
Bug description:
There is a bug in the profile introspection file that results in a
virtual root ns lock being released twice. Introspection from the root
policy namespace is handled correctly it is only when introspection is
done from a task in a sub policy namespace that becomes its virtual ns
root.
This results in the following lockdep trace
[ 78.479744] [ BUG: bad unlock balance detected! ]
[ 78.479792] 3.11.0-11-generic #17 Not tainted
[ 78.479838] -
[ 78.479885] grep/2223 is trying to release lock (&ns->lock) at:
[ 78.479952] [] mutex_unlock+0xe/0x10
[ 78.480002] but there are no more locks to release!
[ 78.480037]
[ 78.480037] other info that might help us debug this:
[ 78.480037] 1 lock held by grep/2223:
[ 78.480037] #0: (&p->lock){+.+.+.}, at: []
seq_read+0x3d/0x3d0
[ 78.480037]
[ 78.480037] stack backtrace:
[ 78.480037] CPU: 0 PID: 2223 Comm: grep Not tainted 3.11.0-11-generic #17
[ 78.480037] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[ 78.480037] 817bf3be 880007763d60 817b97ef
8800189d2190
[ 78.480037] 880007763d88 810e1c6e 88001f044730
8800189d2190
[ 78.480037] 817bf3be 880007763e00 810e5bd6
000724fe56b7
[ 78.480037] Call Trace:
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] dump_stack+0x54/0x74
[ 78.480037] [] print_unlock_imbalance_bug+0xee/0x100
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] lock_release_non_nested+0x226/0x300
[ 78.480037] [] ? __mutex_unlock_slowpath+0xce/0x180
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] lock_release+0xac/0x310
[ 78.480037] [] __mutex_unlock_slowpath+0x83/0x180
[ 78.480037] [] mutex_unlock+0xe/0x10
[ 78.480037] [] p_stop+0x51/0x90
[ 78.480037] [] seq_read+0x288/0x3d0
[ 78.480037] [] vfs_read+0x9e/0x170
[ 78.480037] [] SyS_read+0x4c/0xa0
[ 78.480037] [] system_call_fastpath+0x1a/0x1f
Requires:
user of policy namespaces
root process with in alternate policy namespace reading the
/sys/kernel/security/apparmor/profiles file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1
[Kernel-packages] [Bug 1235977] Re: apparmor bad lock balance during policy introspection
This bug was fixed in the package linux-goldfish - 3.4.0-1.7
---
linux-goldfish (3.4.0-1.7) saucy; urgency=low
[ John Johansen ]
* SAUCE: apparmor: fix unix domain sockets to be mediated on connection
- LP: #1208988
* SAUCE: apparmor: allocate path lookup buffers during init
- LP: #1208988
* SAUCE: apparmor: fix memleak of the profile hash
- LP: #1235523
* SAUCE: apparmor: fix memleak of replacedby struct
- LP: #1235973
* SAUCE: apparmor: fix bad lock balance when introspecting policy
- LP: #1235977
[ Tim Gardner ]
* [Config] Use gcc-4.6 for armhf
- LP: #1236444
-- Andy WhitcroftTue, 08 Oct 2013 11:06:06 +0100
** Branch linked: lp:ubuntu/saucy-proposed/linux-goldfish
** Changed in: linux-goldfish (Ubuntu Saucy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-maguro in Ubuntu.
https://bugs.launchpad.net/bugs/1235977
Title:
apparmor bad lock balance during policy introspection
Status in “linux” package in Ubuntu:
Fix Committed
Status in “linux-goldfish” package in Ubuntu:
Fix Released
Status in “linux-grouper” package in Ubuntu:
Fix Committed
Status in “linux-maguro” package in Ubuntu:
Fix Committed
Status in “linux-mako” package in Ubuntu:
Fix Committed
Status in “linux-manta” package in Ubuntu:
Fix Committed
Status in “linux” source package in Saucy:
Fix Committed
Status in “linux-goldfish” source package in Saucy:
Fix Released
Status in “linux-grouper” source package in Saucy:
Fix Committed
Status in “linux-maguro” source package in Saucy:
Fix Committed
Status in “linux-mako” source package in Saucy:
Fix Committed
Status in “linux-manta” source package in Saucy:
Fix Committed
Bug description:
There is a bug in the profile introspection file that results in a
virtual root ns lock being released twice. Introspection from the root
policy namespace is handled correctly it is only when introspection is
done from a task in a sub policy namespace that becomes its virtual ns
root.
This results in the following lockdep trace
[ 78.479744] [ BUG: bad unlock balance detected! ]
[ 78.479792] 3.11.0-11-generic #17 Not tainted
[ 78.479838] -
[ 78.479885] grep/2223 is trying to release lock (&ns->lock) at:
[ 78.479952] [] mutex_unlock+0xe/0x10
[ 78.480002] but there are no more locks to release!
[ 78.480037]
[ 78.480037] other info that might help us debug this:
[ 78.480037] 1 lock held by grep/2223:
[ 78.480037] #0: (&p->lock){+.+.+.}, at: []
seq_read+0x3d/0x3d0
[ 78.480037]
[ 78.480037] stack backtrace:
[ 78.480037] CPU: 0 PID: 2223 Comm: grep Not tainted 3.11.0-11-generic #17
[ 78.480037] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[ 78.480037] 817bf3be 880007763d60 817b97ef
8800189d2190
[ 78.480037] 880007763d88 810e1c6e 88001f044730
8800189d2190
[ 78.480037] 817bf3be 880007763e00 810e5bd6
000724fe56b7
[ 78.480037] Call Trace:
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] dump_stack+0x54/0x74
[ 78.480037] [] print_unlock_imbalance_bug+0xee/0x100
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] lock_release_non_nested+0x226/0x300
[ 78.480037] [] ? __mutex_unlock_slowpath+0xce/0x180
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] lock_release+0xac/0x310
[ 78.480037] [] __mutex_unlock_slowpath+0x83/0x180
[ 78.480037] [] mutex_unlock+0xe/0x10
[ 78.480037] [] p_stop+0x51/0x90
[ 78.480037] [] seq_read+0x288/0x3d0
[ 78.480037] [] vfs_read+0x9e/0x170
[ 78.480037] [] SyS_read+0x4c/0xa0
[ 78.480037] [] system_call_fastpath+0x1a/0x1f
Requires:
user of policy namespaces
root process with in alternate policy namespace reading the
/sys/kernel/security/apparmor/profiles file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235977/+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 1235977] Re: apparmor bad lock balance during policy introspection
** Also affects: linux-goldfish (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-goldfish (Ubuntu Saucy)
Importance: Undecided => High
** Changed in: linux-goldfish (Ubuntu Saucy)
Status: New => Fix Committed
** Changed in: linux-goldfish (Ubuntu Saucy)
Assignee: (unassigned) => John Johansen (jjohansen)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-maguro in Ubuntu.
https://bugs.launchpad.net/bugs/1235977
Title:
apparmor bad lock balance during policy introspection
Status in “linux” package in Ubuntu:
Fix Committed
Status in “linux-goldfish” package in Ubuntu:
Fix Committed
Status in “linux-grouper” package in Ubuntu:
Fix Committed
Status in “linux-maguro” package in Ubuntu:
Fix Committed
Status in “linux-mako” package in Ubuntu:
Fix Committed
Status in “linux-manta” package in Ubuntu:
Fix Committed
Status in “linux” source package in Saucy:
Fix Committed
Status in “linux-goldfish” source package in Saucy:
Fix Committed
Status in “linux-grouper” source package in Saucy:
Fix Committed
Status in “linux-maguro” source package in Saucy:
Fix Committed
Status in “linux-mako” source package in Saucy:
Fix Committed
Status in “linux-manta” source package in Saucy:
Fix Committed
Bug description:
There is a bug in the profile introspection file that results in a
virtual root ns lock being released twice. Introspection from the root
policy namespace is handled correctly it is only when introspection is
done from a task in a sub policy namespace that becomes its virtual ns
root.
This results in the following lockdep trace
[ 78.479744] [ BUG: bad unlock balance detected! ]
[ 78.479792] 3.11.0-11-generic #17 Not tainted
[ 78.479838] -
[ 78.479885] grep/2223 is trying to release lock (&ns->lock) at:
[ 78.479952] [] mutex_unlock+0xe/0x10
[ 78.480002] but there are no more locks to release!
[ 78.480037]
[ 78.480037] other info that might help us debug this:
[ 78.480037] 1 lock held by grep/2223:
[ 78.480037] #0: (&p->lock){+.+.+.}, at: []
seq_read+0x3d/0x3d0
[ 78.480037]
[ 78.480037] stack backtrace:
[ 78.480037] CPU: 0 PID: 2223 Comm: grep Not tainted 3.11.0-11-generic #17
[ 78.480037] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[ 78.480037] 817bf3be 880007763d60 817b97ef
8800189d2190
[ 78.480037] 880007763d88 810e1c6e 88001f044730
8800189d2190
[ 78.480037] 817bf3be 880007763e00 810e5bd6
000724fe56b7
[ 78.480037] Call Trace:
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] dump_stack+0x54/0x74
[ 78.480037] [] print_unlock_imbalance_bug+0xee/0x100
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] lock_release_non_nested+0x226/0x300
[ 78.480037] [] ? __mutex_unlock_slowpath+0xce/0x180
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] lock_release+0xac/0x310
[ 78.480037] [] __mutex_unlock_slowpath+0x83/0x180
[ 78.480037] [] mutex_unlock+0xe/0x10
[ 78.480037] [] p_stop+0x51/0x90
[ 78.480037] [] seq_read+0x288/0x3d0
[ 78.480037] [] vfs_read+0x9e/0x170
[ 78.480037] [] SyS_read+0x4c/0xa0
[ 78.480037] [] system_call_fastpath+0x1a/0x1f
Requires:
user of policy namespaces
root process with in alternate policy namespace reading the
/sys/kernel/security/apparmor/profiles file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235977/+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 1235977] Re: apparmor bad lock balance during policy introspection
** Changed in: linux (Ubuntu Saucy)
Importance: Undecided => High
** Also affects: linux-grouper (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Saucy)
Status: In Progress => Fix Committed
** Changed in: linux-grouper (Ubuntu Saucy)
Status: New => Fix Committed
** Changed in: linux-grouper (Ubuntu Saucy)
Importance: Undecided => High
** Changed in: linux-grouper (Ubuntu Saucy)
Assignee: (unassigned) => John Johansen (jjohansen)
** Also affects: linux-maguro (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-maguro (Ubuntu Saucy)
Status: New => Fix Committed
** Changed in: linux-maguro (Ubuntu Saucy)
Importance: Undecided => High
** Changed in: linux-maguro (Ubuntu Saucy)
Assignee: (unassigned) => John Johansen (jjohansen)
** Also affects: linux-mako (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-mako (Ubuntu Saucy)
Status: New => Fix Committed
** Changed in: linux-mako (Ubuntu Saucy)
Importance: Undecided => High
** Changed in: linux-mako (Ubuntu Saucy)
Assignee: (unassigned) => John Johansen (jjohansen)
** Also affects: linux-manta (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-manta (Ubuntu Saucy)
Importance: Undecided => High
** Changed in: linux-manta (Ubuntu Saucy)
Status: New => Fix Committed
** Changed in: linux-manta (Ubuntu Saucy)
Assignee: (unassigned) => John Johansen (jjohansen)
--
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/1235977
Title:
apparmor bad lock balance during policy introspection
Status in “linux” package in Ubuntu:
Fix Committed
Status in “linux-grouper” package in Ubuntu:
Fix Committed
Status in “linux-maguro” package in Ubuntu:
Fix Committed
Status in “linux-mako” package in Ubuntu:
Fix Committed
Status in “linux-manta” package in Ubuntu:
Fix Committed
Status in “linux” source package in Saucy:
Fix Committed
Status in “linux-grouper” source package in Saucy:
Fix Committed
Status in “linux-maguro” source package in Saucy:
Fix Committed
Status in “linux-mako” source package in Saucy:
Fix Committed
Status in “linux-manta” source package in Saucy:
Fix Committed
Bug description:
There is a bug in the profile introspection file that results in a
virtual root ns lock being released twice. Introspection from the root
policy namespace is handled correctly it is only when introspection is
done from a task in a sub policy namespace that becomes its virtual ns
root.
This results in the following lockdep trace
[ 78.479744] [ BUG: bad unlock balance detected! ]
[ 78.479792] 3.11.0-11-generic #17 Not tainted
[ 78.479838] -
[ 78.479885] grep/2223 is trying to release lock (&ns->lock) at:
[ 78.479952] [] mutex_unlock+0xe/0x10
[ 78.480002] but there are no more locks to release!
[ 78.480037]
[ 78.480037] other info that might help us debug this:
[ 78.480037] 1 lock held by grep/2223:
[ 78.480037] #0: (&p->lock){+.+.+.}, at: []
seq_read+0x3d/0x3d0
[ 78.480037]
[ 78.480037] stack backtrace:
[ 78.480037] CPU: 0 PID: 2223 Comm: grep Not tainted 3.11.0-11-generic #17
[ 78.480037] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[ 78.480037] 817bf3be 880007763d60 817b97ef
8800189d2190
[ 78.480037] 880007763d88 810e1c6e 88001f044730
8800189d2190
[ 78.480037] 817bf3be 880007763e00 810e5bd6
000724fe56b7
[ 78.480037] Call Trace:
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] dump_stack+0x54/0x74
[ 78.480037] [] print_unlock_imbalance_bug+0xee/0x100
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] lock_release_non_nested+0x226/0x300
[ 78.480037] [] ? __mutex_unlock_slowpath+0xce/0x180
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] lock_release+0xac/0x310
[ 78.480037] [] __mutex_unlock_slowpath+0x83/0x180
[ 78.480037] [] mutex_unlock+0xe/0x10
[ 78.480037] [] p_stop+0x51/0x90
[ 78.480037] [] seq_read+0x288/0x3d0
[ 78.480037] [] vfs_read+0x9e/0x170
[ 78.480037] [] SyS_read+0x4c/0xa0
[ 78.480037] [] system_call_fastpath+0x1a/0x1f
Requires:
user of policy namespaces
root process with in alternate policy namespace reading the
/sys/kernel/security/apparmor/profiles file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235977/+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 1235977] Re: apparmor bad lock balance during policy introspection
** Summary changed:
- apparmor bad lock balance in during policy introspection
+ apparmor bad lock balance during policy introspection
--
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/1235977
Title:
apparmor bad lock balance during policy introspection
Status in “linux” package in Ubuntu:
In Progress
Status in “linux” source package in Saucy:
In Progress
Bug description:
There is a bug in the profile introspection file that results in a
virtual root ns lock being released twice. Introspection from the root
policy namespace is handled correctly it is only when introspection is
done from a task in a sub policy namespace that becomes its virtual ns
root.
This results in the following lockdep trace
[ 78.479744] [ BUG: bad unlock balance detected! ]
[ 78.479792] 3.11.0-11-generic #17 Not tainted
[ 78.479838] -
[ 78.479885] grep/2223 is trying to release lock (&ns->lock) at:
[ 78.479952] [] mutex_unlock+0xe/0x10
[ 78.480002] but there are no more locks to release!
[ 78.480037]
[ 78.480037] other info that might help us debug this:
[ 78.480037] 1 lock held by grep/2223:
[ 78.480037] #0: (&p->lock){+.+.+.}, at: []
seq_read+0x3d/0x3d0
[ 78.480037]
[ 78.480037] stack backtrace:
[ 78.480037] CPU: 0 PID: 2223 Comm: grep Not tainted 3.11.0-11-generic #17
[ 78.480037] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
[ 78.480037] 817bf3be 880007763d60 817b97ef
8800189d2190
[ 78.480037] 880007763d88 810e1c6e 88001f044730
8800189d2190
[ 78.480037] 817bf3be 880007763e00 810e5bd6
000724fe56b7
[ 78.480037] Call Trace:
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] dump_stack+0x54/0x74
[ 78.480037] [] print_unlock_imbalance_bug+0xee/0x100
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] lock_release_non_nested+0x226/0x300
[ 78.480037] [] ? __mutex_unlock_slowpath+0xce/0x180
[ 78.480037] [] ? mutex_unlock+0xe/0x10
[ 78.480037] [] lock_release+0xac/0x310
[ 78.480037] [] __mutex_unlock_slowpath+0x83/0x180
[ 78.480037] [] mutex_unlock+0xe/0x10
[ 78.480037] [] p_stop+0x51/0x90
[ 78.480037] [] seq_read+0x288/0x3d0
[ 78.480037] [] vfs_read+0x9e/0x170
[ 78.480037] [] SyS_read+0x4c/0xa0
[ 78.480037] [] system_call_fastpath+0x1a/0x1f
Requires:
user of policy namespaces
root process with in alternate policy namespace reading the
/sys/kernel/security/apparmor/profiles file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235977/+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
