| To: | xfs-masters@xxxxxxxxxxx |
|---|---|
| Subject: | [Bug 13375] Kernel crash with 2.6.29 + nfs + xfs (radix-tree) |
| From: | bugzilla-daemon@xxxxxxxxxxxxxxxxxxx |
| Date: | Fri, 12 Jun 2009 18:39:17 GMT |
| Auto-submitted: | auto-generated |
| In-reply-to: | <bug-13375-470@xxxxxxxxxxxxxxxxxxxxxxxx/> |
| References: | <bug-13375-470@xxxxxxxxxxxxxxxxxxxxxxxx/> |
http://bugzilla.kernel.org/show_bug.cgi?id=13375 --- Comment #9 from Stephane <sharnois@xxxxxxxxx> 2009-06-12 18:39:14 --- Created an attachment (id=21884) --> (http://bugzilla.kernel.org/attachment.cgi?id=21884) Potential fix in xfs_vnodeops.c Just looks interesting that you would look into the ip for info without the lock. The values of ip->i_update_core or ip->i_itemp could change between the if () and the xfs_ilock. I'm able to reproduced the bug in house so I'll test the change for a few more days, 1 hours is not meaningful. Sorry if this comes has noise and I'm way off. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. |
| Previous by Date: | [Bug 13375] Kernel crash with 2.6.29 + nfs + xfs (radix-tree), bugzilla-daemon |
|---|---|
| Next by Date: | [Bug 13375] Kernel crash with 2.6.29 + nfs + xfs (radix-tree), bugzilla-daemon |
| Previous by Thread: | [Bug 13375] Kernel crash with 2.6.29 + nfs + xfs (radix-tree), bugzilla-daemon |
| Next by Thread: | [Bug 13375] Kernel crash with 2.6.29 + nfs + xfs (radix-tree), bugzilla-daemon |
| Indexes: | [Date] [Thread] [Top] [All Lists] |