** Changed in: linux-ti-omap4 (Ubuntu Natty)
Status: New = Fix Released
** Changed in: linux-ti-omap4 (Ubuntu Oneiric)
Status: Fix Committed = Fix Released
** Changed in: linux-ti-omap4 (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification
** Changed in: linux-ti-omap4 (Ubuntu Oneiric)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791019
Title:
yama_ptracer_del lockdep warning
To manage
This bug was fixed in the package linux - 2.6.38-11.48
---
linux (2.6.38-11.48) natty-proposed; urgency=low
[Herton R. Krzesinski]
* Release Tracking Bug
- LP: #818175
[ Upstream Kernel Changes ]
* Revert HID: magicmouse: ignore 'ivalid report id' while switching
SRU Justification against Ubuntu-2.6.38-11.47:
- does fix the lockdep warning
- normal function is good, and can boot well into natty
see attachment dmesg
** Attachment added: 2.6.38-11-generic.dmsg
In fact, I have done SRU Justification before submitting the patch into
kernel-t...@lists.ubuntu.com.
see
https://lists.ubuntu.com/archives/kernel-team/2011-June/016037.html
I am sure the patch did not affect normal function and only fixed the lockdep
warning, and Tim
already Acked
This bug misses SRU justification, please update this bug with it as explained
on
https://wiki.ubuntu.com/KernelTeam/StableHandbook/StableProcess#Workflow_for_SRU_Patches
Also, this bug is awaiting verification that the kernel in -proposed
solves the problem. Please test the kernel and update
SRU Justification
Impact: yama_ptracer_del can be called in softirq context causing
lockdep warnings
Patch Description: Use spin_lock_bh/spin_unlock_bh to protect list
manipulation against soft IRQ contexts.
** Patch added: UBUNTU: SAUCE: fix yama_ptracer_del lockdep warning
This bug was fixed in the package linux - 3.0.0-4.5
---
linux (3.0.0-4.5) oneiric; urgency=low
[ Ming Lei ]
* SAUCE: fix yama_ptracer_del lockdep warning
- LP: #791019
[ Seth Forshee ]
* SAUCE: (drop after 3.0) asus-wmi: Add callback for hotkey filtering
* SAUCE:
Thanks for catching this! Is this perhaps a problem at a higher level?
(I.e. should security_task_free be called in a different way so that its
hooks (like yama_ptracer_del) do not need to use the _bh locking
mechanisms?
--
You received this bug notification because you are a member of Ubuntu
Now security_task_free is called from __put_task_struct in ubuntu kernel, and
__put_task_struct c
can surely be called in softirq context.In upstream, there are no
security_task_free at all.
If not calling security_task_free, where is it called from? Seems depending on
security
attach another lockdep warning in yama_ptracer_del path.
** Attachment added: yama_ptracer_del-lockdep-warning.log
https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/791019/+attachment/2184345/+files/yama_ptracer_del-lockdep-warning.log
--
You received this bug notification
The attachment patch does fix the warning, yama_ptracer_del can be called in
softirq context, also
can be run in common process context, so use spin_lock_bh to fix it.
** Attachment added: fix_yama_lsm_lockdep_warning.log
** Also affects: linux-ti-omap4 (Ubuntu Natty)
Importance: Undecided
Status: New
** Also affects: linux-ti-omap4 (Ubuntu Oneiric)
Importance: Medium
Assignee: Ming Lei (tom-leiming)
Status: Triaged
** Also affects: linux (Ubuntu)
Importance: Undecided
Status:
** Changed in: linux-ti-omap4 (Ubuntu)
Assignee: (unassigned) = Ming Lei (tom-leiming)
** Changed in: linux-ti-omap4 (Ubuntu)
Importance: Undecided = Medium
** Changed in: linux-ti-omap4 (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a
** Attachment added: yama-lockdep-warning.log
https://bugs.edge.launchpad.net/bugs/791019/+attachment/2149973/+files/yama-lockdep-warning.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791019
15 matches
Mail list logo
