From: Ted Ts'o <tytso@mit.edu>
To: Jiaying Zhang <jiayingz@google.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH RESEND] Free allocated and pre-allocated blocks when check_eofblocks_fl fails
Date: Sun, 10 Jul 2011 20:10:36 -0400 [thread overview]
Message-ID: <20110711001035.GB28763@thunk.org> (raw)
In-Reply-To: <20110622023351.0326042270@ruihe.smo.corp.google.com>
On Tue, Jun 21, 2011 at 07:33:50PM -0700, Jiaying Zhang wrote:
> ext4: free allocated and pre-allocated blocks when check_eofblocks_fl fails
>
> Upon corrupted inode or disk failures, we may fail after we already allocate
> some blocks from the inode or take some blocks from the inode's preallocation
> list, but before we successfully insert the corresponding extent to the extent
> tree. In this case, we should free any allocated blocks and discard the inode's
> preallocated blocks because the entries in the inode's preallocation list may
> be in an inconsistent state.
>
> Signed-off-by: Jiaying Zhang <jiayingz@google.com>
Thanks, added to the ext4 tree. I reformatted the commit description
because its fill width was a bit too large.
- Ted
prev parent reply other threads:[~2011-07-11 0:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 2:33 [PATCH RESEND] Free allocated and pre-allocated blocks when check_eofblocks_fl fails Jiaying Zhang
2011-06-22 9:08 ` Lukas Czerner
2011-07-11 0:10 ` Ted Ts'o [this message]
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=20110711001035.GB28763@thunk.org \
--to=tytso@mit.edu \
--cc=jiayingz@google.com \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).