From: Eric Sandeen <sandeen@sandeen.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org,
Cyrill Gorcunov <gorcunov@gmail.com>
Subject: Re: [PATCH 2/2] Fix possible leakage of blocks in UDF
Date: Sat, 02 Jun 2007 00:17:51 -0500 [thread overview]
Message-ID: <4660FD7F.4090302@sandeen.net> (raw)
In-Reply-To: <20070601154834.53558d1b.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Fri, 01 Jun 2007 17:37:49 -0500
> Eric Sandeen <sandeen@sandeen.net> wrote:
>> going for the inode_lock twice?
>>
>
> lockdep should catch that.
>
hey that's a good idea...! *sigh* sometimes I worry about myself... but
hey at least I got it right. :)
=============================================
[ INFO: possible recursive locking detected ]
2.6.22-rc3 #8
---------------------------------------------
lt-fsstress/3285 is trying to acquire lock:
(inode_lock){--..}, at: [<ffffffff802b0de9>] __mark_inode_dirty+0xe2/0x16c
but task is already holding lock:
(inode_lock){--..}, at: [<ffffffff80316cc9>]
_atomic_dec_and_lock+0x39/0x58
other info that might help us debug this:
3 locks held by lt-fsstress/3285:
#0: (&inode->i_mutex/1){--..}, at: [<ffffffff8029f262>]
do_rmdir+0x7c/0xe3
#1: (&inode->i_mutex){--..}, at: [<ffffffff80462809>]
mutex_lock+0x22/0x24
#2: (inode_lock){--..}, at: [<ffffffff80316cc9>]
_atomic_dec_and_lock+0x39/0x58
stack backtrace:
Call Trace:
[<ffffffff8024e1fc>] __lock_acquire+0x155/0xbaa
[<ffffffff802b0de9>] __mark_inode_dirty+0xe2/0x16c
[<ffffffff8024eccc>] lock_acquire+0x7b/0x9f
[<ffffffff802b0de9>] __mark_inode_dirty+0xe2/0x16c
[<ffffffff80463bc9>] _spin_lock+0x1e/0x28
[<ffffffff802b0de9>] __mark_inode_dirty+0xe2/0x16c
[<ffffffff882dc7cc>] :udf:udf_write_aext+0x101/0x11b
[<ffffffff882e5992>] :udf:extent_trunc+0xd6/0x123
[<ffffffff882e5ab9>] :udf:udf_truncate_tail_extent+0xda/0x171
[<ffffffff882dfc5e>] :udf:udf_drop_inode+0x26/0x35
[<ffffffff802a726d>] iput+0x74/0x76
[<ffffffff802a4e9b>] dentry_iput+0xa0/0xb8
[<ffffffff802a612a>] prune_dcache+0xa2/0x174
[<ffffffff802a4f3c>] d_kill+0x21/0x43
[<ffffffff802a5eef>] prune_one_dentry+0x3a/0xef
[<ffffffff802a6175>] prune_dcache+0xed/0x174
[<ffffffff802a6253>] shrink_dcache_parent+0x21/0x10e
[<ffffffff8029becd>] dentry_unhash+0x26/0x84
[<ffffffff8029d23c>] vfs_rmdir+0x88/0x117
[<ffffffff8029f287>] do_rmdir+0xa1/0xe3
[<ffffffff8020cf4b>] syscall_trace_enter+0x8d/0x8f
[<ffffffff8029f300>] sys_rmdir+0x11/0x13
[<ffffffff80209da5>] tracesys+0xdc/0xe1
-Eric
next prev parent reply other threads:[~2007-06-02 5:18 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 16:59 [PATCH 1/2] Fix possible UDF data corruption Jan Kara
2007-05-24 17:05 ` [PATCH 2/2] Fix possible leakage of blocks in UDF Jan Kara
2007-05-24 20:36 ` Jan Kara
2007-05-30 21:46 ` Eric Sandeen
2007-05-30 22:22 ` Eric Sandeen
2007-05-31 16:48 ` Cyrill Gorcunov
2007-05-31 17:42 ` Cyrill Gorcunov
2007-05-31 17:46 ` Eric Sandeen
2007-06-01 16:49 ` Cyrill Gorcunov
2007-06-01 17:04 ` Andrew Morton
2007-06-01 17:15 ` Cyrill Gorcunov
2007-06-01 17:17 ` Eric Sandeen
2007-06-01 17:48 ` Cyrill Gorcunov
2007-06-01 17:51 ` Eric Sandeen
2007-06-01 17:52 ` Cyrill Gorcunov
2007-06-01 18:20 ` Cyrill Gorcunov
2007-06-01 21:10 ` Jan Kara
2007-06-01 21:05 ` Eric Sandeen
2007-06-01 22:37 ` Eric Sandeen
2007-06-01 22:48 ` Andrew Morton
2007-06-02 5:17 ` Eric Sandeen [this message]
2007-06-02 5:43 ` Andrew Morton
2007-06-02 6:34 ` Cyrill Gorcunov
2007-06-02 6:54 ` Andrew Morton
2007-06-02 6:59 ` Cyrill Gorcunov
2007-06-02 7:06 ` Andrew Morton
2007-06-02 14:06 ` Cyrill Gorcunov
2007-06-02 17:32 ` Andrew Morton
2007-06-02 18:57 ` Cyrill Gorcunov
2007-06-02 19:16 ` Andrew Morton
2007-06-02 20:01 ` Cyrill Gorcunov
2007-06-02 22:49 ` Andrew Morton
2007-06-03 6:28 ` Cyrill Gorcunov
2007-06-03 7:22 ` Cyrill Gorcunov
2007-06-04 15:53 ` Cyrill Gorcunov
2007-05-24 17:20 ` [PATCH 1/2] Fix possible UDF data corruption Cyrill Gorcunov
2007-05-24 18:35 ` Andrew Morton
2007-05-24 18:53 ` Cyrill Gorcunov
2007-05-24 19:23 ` Cyrill Gorcunov
2007-05-24 19:36 ` Andrew Morton
2007-05-24 19:49 ` Cyrill Gorcunov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4660FD7F.4090302@sandeen.net \
--to=sandeen@sandeen.net \
--cc=akpm@linux-foundation.org \
--cc=gorcunov@gmail.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox