* Release Tracking Bug
- LP: #1104061
* Revert "fsnotify: change locking order"
- LP: #1101666
* Revert "fsnotify: dont put marks on temporary list when clearing marks
by group"
- LP: #1101666
* Revert "fsnotify: introduce locked versions of fsnotify_add_mark() and
fsnotify_remove_mark()"
- LP: #1101666
* Revert "fsnotify: pass group to fsnotify_destroy_mark()"
- LP: #1101666
* Revert "fsnotify: use a mutex instead of a spinlock to protect a groups
mark list"
- LP: #1101666
* Revert "fanotify: add an extra flag to mark_remove_from_mask that
indicates wheather a mark should be destroyed"
- LP: #1101666
* Revert "fsnotify: take groups mark_lock before mark lock"
- LP: #1101666
* Revert "fsnotify: use reference counting for groups"
- LP: #1101666
* Revert "fsnotify: introduce fsnotify_get_group()"
- LP: #1101666
-- Ike Panhc <email address hidden> Fri, 25 Jan 2013 09:45:57 +0800
This bug was fixed in the package linux-armadaxp - 3.2.0-1614.19
---------------
linux-armadaxp (3.2.0-1614.19) precise-proposed; urgency=low
[ Ike Panhc ]
* Release Tracking Bug
- LP: #1105115
* Rebase onto Ubuntu-3.2.0-37.58
[ Ubuntu: 3.2.0-37.58 ]
* Release Tracking Bug remove_ mark()" destroy_ mark()" from_mask that get_group( )"
- LP: #1104061
* Revert "fsnotify: change locking order"
- LP: #1101666
* Revert "fsnotify: dont put marks on temporary list when clearing marks
by group"
- LP: #1101666
* Revert "fsnotify: introduce locked versions of fsnotify_add_mark() and
fsnotify_
- LP: #1101666
* Revert "fsnotify: pass group to fsnotify_
- LP: #1101666
* Revert "fsnotify: use a mutex instead of a spinlock to protect a groups
mark list"
- LP: #1101666
* Revert "fanotify: add an extra flag to mark_remove_
indicates wheather a mark should be destroyed"
- LP: #1101666
* Revert "fsnotify: take groups mark_lock before mark lock"
- LP: #1101666
* Revert "fsnotify: use reference counting for groups"
- LP: #1101666
* Revert "fsnotify: introduce fsnotify_
- LP: #1101666
-- Ike Panhc <email address hidden> Fri, 25 Jan 2013 09:45:57 +0800