Messages in this thread | | | Date | Fri, 1 Jun 2007 15:48:34 -0700 | From | Andrew Morton <> | Subject | Re: [PATCH 2/2] Fix possible leakage of blocks in UDF |
| |
On Fri, 01 Jun 2007 17:37:49 -0500 Eric Sandeen <sandeen@sandeen.net> wrote:
> Jan Kara wrote: > > Thanks for info - I'm now mostly out of email for a few days but I'll > > have a look at it as soon as I return. > > > > Honza > > Here we go: > > [1]kdb> btp 3263 > Stack traceback for pid 3263 > 0xffff81006f1b8100 3263 3247 1 0 R 0xffff81006f1b83d0 > lt-fsstress > rsp rip Function (args) > 0xffff81006f335c48 0xffffffff8044b989 _spin_lock+0x7 > 0xffff81006f335c70 0xffffffff802a914b __mark_inode_dirty+0xe0 > 0xffff81006f335ca0 0xffffffff882d47d0 [udf]udf_write_aext+0x101 > 0xffff81006f335cd0 0xffffffff882dd95a [udf]extent_trunc+0xd6 > 0xffff81006f335d20 0xffffffff882dda81 [udf]udf_truncate_tail_extent+0xda > 0xffff81006f335da0 0xffffffff882d7c26 [udf]udf_drop_inode+0x26 > 0xffff81006f335db0 0xffffffff8029f816 iput+0x74 > 0xffff81006f335dc0 0xffffffff8029d6a8 dentry_iput+0x8f > 0xffff81006f335de0 0xffffffff8029d748 d_kill+0x21 > 0xffff81006f335e00 0xffffffff8029e450 prune_one_dentry+0x3a > 0xffff81006f335e20 0xffffffff8029e5e8 prune_dcache+0xe3 > 0xffff81006f335e50 0xffffffff8029e6bf shrink_dcache_parent+0x21 > 0xffff81006f335e80 0xffffffff80294a27 dentry_unhash+0x1d > 0xffff81006f335e90 0xffffffff80295d43 vfs_rmdir+0x88 > 0xffff81006f335eb0 0xffffffff80297d5b do_rmdir+0x9c > 0xffff81006f335f40 0xffffffff8020ce23 syscall_trace_enter+0x8d > 0xffff81006f335f70 0xffffffff80297dd4 sys_rmdir+0x11 > 0xffff81006f335f80 0xffffffff80209d5c tracesys+0xdc > > going for the inode_lock twice? >
lockdep should catch that. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |