public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Eric Sandeen <sandeen@sandeen.net>, Jan Kara <jack@suse.cz>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Fix possible leakage of blocks in UDF
Date: Sat, 2 Jun 2007 10:32:03 -0700	[thread overview]
Message-ID: <20070602103203.e39d25ed.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070602140619.GA10303@cvg>

On Sat, 2 Jun 2007 18:06:19 +0400 Cyrill Gorcunov <gorcunov@gmail.com> wrote:

> [Andrew Morton - Sat, Jun 02, 2007 at 12:06:45AM -0700]
> | On Sat, 2 Jun 2007 10:59:23 +0400 Cyrill Gorcunov <gorcunov@gmail.com> wrote:
> | 
> | > [Andrew Morton - Fri, Jun 01, 2007 at 11:54:22PM -0700]
> | > | On Sat, 2 Jun 2007 10:34:03 +0400 Cyrill Gorcunov <gorcunov@gmail.com> wrote:
> | > | 
> | > | > | That patch is DOA, methinks.
> | > | > | 
> | > | > 
> | > | > Andrew, what does it mean - "DOA"? Dead on arrival?
> | > | 
> | > | yes - I dropped it.
> | > | 
> | > 
> | > But that could lead to rejection of my code-style-conversion patch...
> | > Should I remake them?
> | 
> | Actually I've rebuilt those patches four times already.  People keep
> | changing stuff.
> | 
> | > Actually Jan was right, the current state of UDF (without his patches)
> | > could lead to lost blocks and his patch must be just fixed I think.
> | 
> | sure.
> | 
> 
> Andrew, you know I've been trying to reproduce Eric's lockup case almost
> two hour and still can't reach it. All manupulation I've done to UDF didn't
> lead to lockup. Moreover, I've added debug print for UDF module and here is
> the results (for single drop_inode call):
> 
> 	[12063.897000] UDF: udf_drop_inode:105 --> udf_drop_inode --> inode->i_count: 0
> 	[12063.897000] UDF: udf_drop_inode:107 udf_drop_inode -> discard_prealloc
> 	[12063.897000] UDF: udf_discard_prealloc:136 udf_discard_prealloc
> 	[12063.897000] UDF: udf_truncate_tail_extent:84 udf_truncate_tail_extent
> 	[12063.897000] UDF: udf_truncate_extents:194 udf_truncate_extents -->
> 	[12063.897000] UDF: extent_trunc:38 --->
> 	[12063.897000] UDF: extent_trunc:54 call to udf_write_aext
> 	[12063.897000] UDF: udf_write_aext:1843 udf_write_aext
> 	[12063.897000] UDF: udf_write_aext:1846 dont has epos->bh
> 	[12063.897000] UDF: udf_write_aext:1866 ICBTAG_FLAG_AD_LONG
> --->	[12063.897000] UDF: udf_write_aext:1893 ---> gotcha ---> call mark_inode_dirty
> --->	[12063.897000] UDF: extent_trunc:59 --> gotcha --> call mark_inode_dirty
> 	[12063.897000] UDF: extent_trunc:68 <---
> --->	[12063.897000] UDF: udf_truncate_extents:282 call mark_inode_dirty
> 	[12063.897000] UDF: udf_truncate_extents:330 udf_truncate_extents <--
> 	[12063.897000] UDF: udf_drop_inode:115 <-- udf_drop_inode <--
> 
> As you may see, mark_inode_dirty is called several time and no locking happened.
> Maybe I should use some test utils?
> 

Silly question: you _do_ have CONFIG_SMP=y, yes?

And did you enable lockdep?

  reply	other threads:[~2007-06-02 17:32 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
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 [this message]
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=20070602103203.e39d25ed.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=gorcunov@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    /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