Bug 784733 - BUG at kernel/rtmutex.c:472 MRG 2.1 3.0.9-rt26.45.el6rt.x86_64 kernel
Summary: BUG at kernel/rtmutex.c:472 MRG 2.1 3.0.9-rt26.45.el6rt.x86_64 kernel
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: realtime-kernel
Version: 2.1
Hardware: x86_64
OS: All
urgent
urgent
Target Milestone: 2.1.4
: ---
Assignee: Steven Rostedt
QA Contact: David Sommerseth
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-25 23:40 UTC by IBM Bug Proxy
Modified: 2016-05-22 23:34 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
When a sleeping task, waiting on a futex (fast userspace mutex), tried to get the spin_lock(hb->lock) RT-mutex, if the owner of the futex released the lock, the sleeping task was put on a futex proxy lock. Consequently, the sleeping task was blocked on two locks and eventually terminated in the BUG_ON() function. With this update, the WAKEUP_INPROGRESS pseudo-lock has been added to be used as a proxy lock. This pseudo-lock tells the sleeping task that it is being woken up so that the task no longer tries to get the second lock. Now, the futex code works as expected and sleeping tasks no longer crash in the described scenario.
Clone Of:
Environment:
Last Closed: 2012-02-23 20:24:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
IBM Linux Technology Center 78072 0 None None None Never
Red Hat Product Errata RHSA-2012:0333 0 normal SHIPPED_LIVE Important: kernel-rt security and bug fix update 2012-02-24 01:21:35 UTC

Description IBM Bug Proxy 2012-01-25 23:40:34 UTC 
-- Problem Description --
Our Java testing team was having issues with MRG 2.1 on AMD systems.  Therefore, we started our normal release testing on a LS22.  Shortly after starting the tests, the system crashed.  The following stack traces were in the system log.


Jan 25 07:09:16 elm3b207 kernel: ------------[ cut here ]------------
Jan 25 07:09:16 elm3b207 kernel: kernel BUG at kernel/rtmutex.c:472!
Jan 25 07:09:16 elm3b207 kernel: invalid opcode: 0000 [#1] PREEMPT SMP 
Jan 25 07:09:16 elm3b207 kernel: CPU 2 
Jan 25 07:09:16 elm3b207 kernel: Modules linked in: autofs4 sunrpc ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables ip6t_REJECT xt_tcpudp nf_conntrack_ipv6 nf_defrag_ipv6 xt_state ip6table_filter ip6_tables x_tables ipv6 sr_mod cdrom joydev ums_cypress sg microcode bnx2 serio_raw pcspkr amd64_edac_mod edac_core shpchp usb_storage ext4 mbcache jbd2 crc16 sd_mod crc_t10dif ehci_hcd ohci_hcd mptsas mptscsih mptbase scsi_transport_sas button radeon ttm drm_kms_helper drm hwmon i2c_algo_bit i2c_core power_supply dm_mirror dm_region_hash dm_log dm_mod [last unloaded: scsi_wait_scan]
Jan 25 07:09:16 elm3b207 kernel:
Jan 25 07:09:16 elm3b207 kernel: Pid: 3689, comm: java Not tainted 3.0.9-rt26.45.el6rt.x86_64 #1 IBM BladeCenter LS42 -[7901AC1]-/Server Blade
Jan 25 07:09:16 elm3b207 kernel: RIP: 0010:[<ffffffff8106f5ef>]  [<ffffffff8106f5ef>] task_blocks_on_rt_mutex+0x76/0x211
Jan 25 07:09:16 elm3b207 kernel: RSP: 0000:ffff88041d231c68  EFLAGS: 00210082
Jan 25 07:09:16 elm3b207 kernel: RAX: ffff88041d73a300 RBX: ffff88041af69cb8 RCX: 0000000000000001
Jan 25 07:09:16 elm3b207 kernel: RDX: 0000000000004a4a RSI: ffff88041af69cb8 RDI: ffff88041c712840
Jan 25 07:09:16 elm3b207 kernel: RBP: ffff88041d231cc8 R08: ffff88041c712240 R09: 31c8000000000000
Jan 25 07:09:16 elm3b207 kernel: R10: ffff88041d231c78 R11: 0000000000200286 R12: ffff88041d73a301
Jan 25 07:09:16 elm3b207 kernel: R13: ffff88041c712840 R14: ffff88041ba1d750 R15: 0000000000000001
Jan 25 07:09:16 elm3b207 kernel: FS:  00007f92a94937a0(0000) GS:ffff88042fc40000(0063) knlGS:00000000b84c1b70
Jan 25 07:09:16 elm3b207 kernel: CS:  0010 DS: 002b ES: 002b CR0: 0000000080050033
Jan 25 07:09:16 elm3b207 kernel: CR2: 00007f92a94a3000 CR3: 000000041bdd3000 CR4: 00000000000006e0
Jan 25 07:09:16 elm3b207 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jan 25 07:09:16 elm3b207 kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Jan 25 07:09:16 elm3b207 kernel: Process java (pid: 3689, threadinfo ffff88041d230000, task ffff88041d73a300)
Jan 25 07:09:16 elm3b207 kernel: Stack:
Jan 25 07:09:16 elm3b207 kernel: 0000000000000000 0000000000000000 ffff88041d231cf8 ffff88041c712240
Jan 25 07:09:16 elm3b207 kernel: 0000000000200292 80000e688103af68 ffff88041d231d98 ffff88041ba1d750
Jan 25 07:09:16 elm3b207 kernel: ffff88041af69cb8 ffff88041c712240 0000000000000001 0000000000000001
Jan 25 07:09:16 elm3b207 kernel: Call Trace:
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8106f7df>] rt_mutex_start_proxy_lock+0x55/0x8a
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8106dd6d>] futex_requeue+0x498/0x607
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff813993a6>] ? _raw_spin_unlock_irqrestore+0x25/0x30
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8106e733>] do_futex+0x857/0x8a1
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8110c197>] ? path_put+0x22/0x26
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8106e9e4>] compat_sys_futex+0x128/0x140
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff813a03b3>] ia32_do_call+0x13/0x13
Jan 25 07:09:16 elm3b207 kernel: Code: 20 49 83 b8 18 06 00 00 01 75 16 48 8b 75 c0 4c 89 ef e8 a6 9d 32 00 b8 f5 ff ff ff e9 96 01 00 00 49 83 b8 18 06 00 00 01 76 04 <0f> 0b eb fe 4c 89 c7 4c 89 45 b8 e8 c5 f8 ff ff 4c 8b 45 b8 4c 
Jan 25 07:09:16 elm3b207 kernel: RIP  [<ffffffff8106f5ef>] task_blocks_on_rt_mutex+0x76/0x211
Jan 25 07:09:16 elm3b207 kernel: RSP <ffff88041d231c68>
Jan 25 07:09:16 elm3b207 kernel: ---[ end trace 0000000000000002 ]---
Jan 25 07:09:16 elm3b207 kernel: note: java[3689] exited with preempt_count 2
Jan 25 07:09:16 elm3b207 kernel: ------------[ cut here ]------------
Jan 25 07:09:16 elm3b207 kernel: kernel BUG at kernel/rtmutex.c:724!
Jan 25 07:09:16 elm3b207 kernel: invalid opcode: 0000 [#2] PREEMPT SMP 
Jan 25 07:09:16 elm3b207 kernel: CPU 2 
Jan 25 07:09:16 elm3b207 kernel: Modules linked in: autofs4 sunrpc ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables ip6t_REJECT xt_tcpudp nf_conntrack_ipv6 nf_defrag_ipv6 xt_state ip6table_filter ip6_tables x_tables ipv6 sr_mod cdrom joydev ums_cypress sg microcode bnx2 serio_raw pcspkr amd64_edac_mod edac_core shpchp usb_storage ext4 mbcache jbd2 crc16 sd_mod crc_t10dif ehci_hcd ohci_hcd mptsas mptscsih mptbase scsi_transport_sas button radeon ttm drm_kms_helper drm hwmon i2c_algo_bit i2c_core power_supply dm_mirror dm_region_hash dm_log dm_mod [last unloaded: scsi_wait_scan]
Jan 25 07:09:16 elm3b207 kernel:
Jan 25 07:09:16 elm3b207 kernel: Pid: 3689, comm: java Tainted: G      D      3.0.9-rt26.45.el6rt.x86_64 #1 IBM BladeCenter LS42 -[7901AC1]-/Server Blade
Jan 25 07:09:16 elm3b207 kernel: RIP: 0010:[<ffffffff8139892f>]  [<ffffffff8139892f>] rt_spin_lock_slowlock+0x70/0x217
Jan 25 07:09:16 elm3b207 kernel: RSP: 0000:ffff88041d231818  EFLAGS: 00210246
Jan 25 07:09:16 elm3b207 kernel: RAX: ffff88041d73a300 RBX: ffffffff817bc860 RCX: 0000000000000001
Jan 25 07:09:16 elm3b207 kernel: RDX: ffffffff817bc878 RSI: ffff88041d73a300 RDI: ffff88041d73a301
Jan 25 07:09:16 elm3b207 kernel: RBP: ffff88041d2318c8 R08: 0000000050a0f0ab R09: 0000000000000000
Jan 25 07:09:16 elm3b207 kernel: R10: 0000000000000000 R11: 0000000000200202 R12: ffff88041d73a300
Jan 25 07:09:16 elm3b207 kernel: R13: ffff88041d73a300 R14: 0000000000000006 R15: ffff88041d2318f8
Jan 25 07:09:16 elm3b207 kernel: FS:  00007f92a94937a0(0000) GS:ffff88042fc40000(0063) knlGS:00000000b84c1b70
Jan 25 07:09:16 elm3b207 kernel: CS:  0010 DS: 002b ES: 002b CR0: 0000000080050033
Jan 25 07:09:16 elm3b207 kernel: CR2: 00007f92a94a3000 CR3: 000000041bdd3000 CR4: 00000000000006e0
Jan 25 07:09:16 elm3b207 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jan 25 07:09:16 elm3b207 kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Jan 25 07:09:16 elm3b207 kernel: Process java (pid: 3689, threadinfo ffff88041d230000, task ffff88041d73a300)
Jan 25 07:09:16 elm3b207 kernel: Stack:
Jan 25 07:09:16 elm3b207 kernel: ffffffff817b535e ffffffff8155826c ffff88041d231978 ffffffff817b535f
Jan 25 07:09:16 elm3b207 kernel: ffff88041d231898 ffffffff8139f6ce ffff88041d2318d8 0000000000000400
Jan 25 07:09:16 elm3b207 kernel: 0000000000000000 0000000000000000 0000000000000000 0000000050a0f0ab
Jan 25 07:09:16 elm3b207 kernel: Call Trace:
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8139f6ce>] ? apic_timer_interrupt+0xe/0x20
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff81398ff6>] rt_spin_lock+0x24/0x26
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8106c2ae>] exit_pi_state_list+0x8a/0x144
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8103d630>] mm_release+0x73/0xeb
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff81041b6e>] exit_mm+0x26/0x137
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff810433a7>] do_exit+0x277/0x7e3
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8103febe>] ? kmsg_dump+0xe3/0xf2
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8139a2e6>] oops_end+0xb6/0xbe
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff81004c56>] die+0x5a/0x63
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff81399d49>] do_trap+0x121/0x130
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff81002f7f>] do_invalid_op+0x96/0x9f
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8106f5ef>] ? task_blocks_on_rt_mutex+0x76/0x211
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8139fc95>] invalid_op+0x15/0x20
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8106f5ef>] ? task_blocks_on_rt_mutex+0x76/0x211
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8106f5af>] ? task_blocks_on_rt_mutex+0x36/0x211
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8106f7df>] rt_mutex_start_proxy_lock+0x55/0x8a
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8106dd6d>] futex_requeue+0x498/0x607
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff813993a6>] ? _raw_spin_unlock_irqrestore+0x25/0x30
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8106e733>] do_futex+0x857/0x8a1
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8110c197>] ? path_put+0x22/0x26
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8106e9e4>] compat_sys_futex+0x128/0x140
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff813a03b3>] ia32_do_call+0x13/0x13
Jan 25 07:09:16 elm3b207 kernel: Code: 48 89 43 10 31 d2 b9 01 00 00 00 4c 89 e6 48 89 df e8 df 63 cd ff 85 c0 0f 85 9a 01 00 00 48 8b 43 18 48 83 e0 fe 49 39 c4 75 04 <0f> 0b eb fe 4d 8d ac 24 00 06 00 00 4c 8d bd 60 ff ff ff 65 4c 
Jan 25 07:09:16 elm3b207 kernel: RIP  [<ffffffff8139892f>] rt_spin_lock_slowlock+0x70/0x217
Jan 25 07:09:16 elm3b207 kernel: RSP <ffff88041d231818>
Jan 25 07:09:16 elm3b207 kernel: ---[ end trace 0000000000000003 ]---
Jan 25 07:09:16 elm3b207 kernel: Fixing recursive fault but reboot is needed!
Jan 25 07:09:16 elm3b207 kernel: BUG: scheduling while atomic: java/3689/0x00000004
Jan 25 07:09:16 elm3b207 kernel: Modules linked in: autofs4 sunrpc ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables ip6t_REJECT xt_tcpudp nf_conntrack_ipv6 nf_defrag_ipv6 xt_state ip6table_filter ip6_tables x_tables ipv6 sr_mod cdrom joydev ums_cypress sg microcode bnx2 serio_raw pcspkr amd64_edac_mod edac_core shpchp usb_storage ext4 mbcache jbd2 crc16 sd_mod crc_t10dif ehci_hcd ohci_hcd mptsas mptscsih mptbase scsi_transport_sas button radeon ttm drm_kms_helper drm hwmon i2c_algo_bit i2c_core power_supply dm_mirror dm_region_hash dm_log dm_mod [last unloaded: scsi_wait_scan]
Jan 25 07:09:16 elm3b207 kernel: Pid: 3689, comm: java Tainted: G      D      3.0.9-rt26.45.el6rt.x86_64 #1
Jan 25 07:09:16 elm3b207 kernel: Call Trace:
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff81035918>] __schedule_bug+0x5c/0x61
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff813971a0>] __schedule+0x9f/0x5d8
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff81040a25>] ? vprintk+0x429/0x46e
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8139700f>] ? printk+0x41/0x4a
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff81397b3b>] schedule+0x77/0x93
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff81043256>] do_exit+0x126/0x7e3
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8103febe>] ? kmsg_dump+0xe3/0xf2
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8139a2e6>] oops_end+0xb6/0xbe
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff81004c56>] die+0x5a/0x63
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff81399d49>] do_trap+0x121/0x130
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff81002f7f>] do_invalid_op+0x96/0x9f
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8139892f>] ? rt_spin_lock_slowlock+0x70/0x217
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff811c06b1>] ? vsnprintf+0x3ee/0x42a
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8139fc95>] invalid_op+0x15/0x20
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8139892f>] ? rt_spin_lock_slowlock+0x70/0x217
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8139891a>] ? rt_spin_lock_slowlock+0x5b/0x217
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8139f6ce>] ? apic_timer_interrupt+0xe/0x20
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff81398ff6>] rt_spin_lock+0x24/0x26
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8106c2ae>] exit_pi_state_list+0x8a/0x144
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8103d630>] mm_release+0x73/0xeb
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff81041b6e>] exit_mm+0x26/0x137
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff810433a7>] do_exit+0x277/0x7e3
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8103febe>] ? kmsg_dump+0xe3/0xf2
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8139a2e6>] oops_end+0xb6/0xbe
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff81004c56>] die+0x5a/0x63
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff81399d49>] do_trap+0x121/0x130
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff81002f7f>] do_invalid_op+0x96/0x9f
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8106f5ef>] ? task_blocks_on_rt_mutex+0x76/0x211
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8139fc95>] invalid_op+0x15/0x20
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8106f5ef>] ? task_blocks_on_rt_mutex+0x76/0x211
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8106f5af>] ? task_blocks_on_rt_mutex+0x36/0x211
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8106f7df>] rt_mutex_start_proxy_lock+0x55/0x8a
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8106dd6d>] futex_requeue+0x498/0x607
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff813993a6>] ? _raw_spin_unlock_irqrestore+0x25/0x30
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8106e733>] do_futex+0x857/0x8a1
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8110c197>] ? path_put+0x22/0x26
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff8106e9e4>] compat_sys_futex+0x128/0x140
Jan 25 07:09:16 elm3b207 kernel: [<ffffffff813a03b3>] ia32_do_call+0x13/0x13

This BUG is with their MRG 2.1 release candidate.
Comment 1 Steven Rostedt 2012-01-28 01:10:39 UTC 
Looks like this is due to the futex_requeue work done by Darren Hart. It sets up a proxy lock when requeueing with a PI futex. My hunch is the waiter that is being requeued is some how blocked on an rt spin lock turned mutex. Trying to add it to a PI lock where it is already attached to a PI lock will cause this bug.

This is just a hunch. More analysis would be needed.
Comment 8 Steven Rostedt 2012-02-09 16:02:55 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: sleeping task waiting on futex waking up and trying to grab spin_lock(hb->lock), which on MRG is an rtmutex, while the owner of futex, releases it putting sleeping task on futex proxy lock, causing the sleeping task to blocked on two locks

Consequence: The sleeping task hits a BUG_ON() because it can not sleep on two locks at the same time.

Fix: Add another pseudo lock WAKEUP_INPROGRESS to set the proxy lock to, that will tell the sleeping task that it is being woken up and that it wont try to grab the second lock.

Result: Task no longer crashes and the futex code works as designed.
Comment 10 IBM Bug Proxy 2012-02-15 23:20:26 UTC 
------- Comment From niv.com 2012-02-15 18:15 EDT-------
Closing bug on IBM side. Steven's patch fixed this issue and updated MRG 2.1 eraly errata kernel rpms (.50) also passed testing with the JTC reproduction scenario (See bug #78082).
Comment 11 Tomas Capek 2012-02-22 16:10:07 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,7 +1 @@
-Cause: sleeping task waiting on futex waking up and trying to grab spin_lock(hb->lock), which on MRG is an rtmutex, while the owner of futex, releases it putting sleeping task on futex proxy lock, causing the sleeping task to blocked on two locks
+When a sleeping task, waiting on a futex (fast userspace mutex), tried to get the spin_lock(hb->lock) RT-mutex, if the owner of the futex released the lock, the sleeping task was put on a futex proxy lock. Consequently, the sleeping task was blocked on two locks and eventually terminated in the BUG_ON() function. With this update, the WAKEUP_INPROGRESS pseudo-lock has been added to be used as a proxy lock. This pseudo-lock tells the sleeping task that it is being woken up so that the task no longer tries to get the second lock. Now, the futex code works as expected and sleeping tasks no longer crash in the described scenario.-
-Consequence: The sleeping task hits a BUG_ON() because it can not sleep on two locks at the same time.
-
-Fix: Add another pseudo lock WAKEUP_INPROGRESS to set the proxy lock to, that will tell the sleeping task that it is being woken up and that it wont try to grab the second lock.
-
-Result: Task no longer crashes and the futex code works as designed.
Comment 12 errata-xmlrpc 2012-02-23 20:24:30 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-0333.html
Note You need to log in before you can comment on or make changes to this bug.