http://bugzilla.kernel.org/show_bug.cgi?id=6877
------- Additional Comments From smurf@xxxxxxxxxxxxxx 2006-08-04 23:47 -------
Somewhat different call chain here, but same effect (and, helpfully, no
irrepairable file system damage -- though I did have a corrupted journal).
This bug is a showstopper for 2.6.18. :-/
EIP: [<f8c01497>] xfs_btree_init_cursor+0x37/0x12f [xfs] SS:ESP 0068:d61cdbd0
[<f8be8d0a>] xfs_free_ag_extent+0x29/0x58a [xfs]
[<f8bea416>] xfs_free_extent+0xb2/0xce [xfs]
[<f8bf35b3>] xfs_bmap_finish+0xd8/0x156 [xfs]
[<f8c13d0e>] xfs_itruncate_finish+0x1be/0x2b5 [xfs]
[<f8c2da82>] xfs_setattr+0x7de/0xcc9 [xfs]
[<f8c382b3>] xfs_vn_setattr+0x110/0x12d [xfs]
[<b016b9ee>] notify_change+0x139/0x26b
[<b015315b>] do_truncate+0x53/0x6c
[<b01613a4>] may_open+0x171/0x193
[<b016329c>] open_namei+0x255/0x5e6
[<b01544ae>] do_filp_open+0x1f/0x35
[<b01545ca>] do_sys_open+0x3f/0xba
[<b0154671>] sys_open+0x16/0x18
[<b01029b3>] syscall_call+0x7/0xb
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
|