linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: Rich Coe <Richard.Coe@med.ge.com>
Cc: torvalds@osdl.org, jack@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: PATCH: udf fs corruption on linux-2.6
Date: Wed, 13 Jun 2007 17:27:28 -0400	[thread overview]
Message-ID: <46706140.6040502@redhat.com> (raw)
In-Reply-To: <20070613154803.a1ad874a.Richard.Coe@med.ge.com>

On 06/13/2007 04:48 PM, Rich Coe wrote:
> Hi Linus, 
> 
> This patch fixes directory and missing files corruption in fs/udf which
> occurs on all known 2.6 releases.
> 
> The corruption occurs because blocks which were pre-alloc'd for a directory 
> are released back to the fs freelist, but the inode's alloc block information
> is not updated to reflect this.
> 
> You would not see corruption if the number of files in any directory is 
> less than 41, because the pre-alloc routine does not allocate blocks for the
> directory until the number of files is over 40.
> 
> The problem occurs during unmounting because fs/udf incorrectly calls 
> udf_discard_prealloc() from udf_clear_inode().  udf_discard_prealloc() will
> update the inode and schedule it for write, but no write will ever occur 
> because the fs is in the process of being umount'd. 
> 
> The solution is to add a put_inode routine to update the inode contents
> and release the pre-alloc'd blocks to disk prior to clearing the inode
> from the kernel.

http://lkml.org/lkml/2007/6/11/79


  reply	other threads:[~2007-06-13 21:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-13 20:48 PATCH: udf fs corruption on linux-2.6 Rich Coe
2007-06-13 21:27 ` Chuck Ebbert [this message]
2007-06-14  8:25 ` Jan Kara
2007-06-14 21:32 ` RFC: " Rich Coe
2007-06-14 22:12   ` Linus Torvalds
2007-06-15 16:09     ` Jan Kara
2007-06-15 23:23       ` Linus Torvalds

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=46706140.6040502@redhat.com \
    --to=cebbert@redhat.com \
    --cc=Richard.Coe@med.ge.com \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).