From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: tytso@mit.edu, cmm@us.ibm.com
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: Don't claim block from group which has corrupt bitmap
Date: Mon, 11 Feb 2008 17:06:52 +0530 [thread overview]
Message-ID: <20080211113652.GA3833@skywalker> (raw)
In-Reply-To: <1202729418-5582-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
On Mon, Feb 11, 2008 at 05:00:18PM +0530, Aneesh Kumar K.V wrote:
> In ext4_mb_complex_scan_group, if the extent length of the newly
> found extentet is greater than than the total free blocks counted
> in group info, break without claiming the block.
>
> Document different ext4_error usage, explaining the state with which we
> continue if we mount with errors=continue
>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> ---
> fs/ext4/mballoc.c | 16 +++++++++++++++-
> 1 files changed, 15 insertions(+), 1 deletions(-)
This was actually part of the version 2 of the patch
ext4_avoid_panic_in_case_of_corrupted_bitmap.patch. But we missed it
in the last update. So sending it as a separate patch.
-aneesh
prev parent reply other threads:[~2008-02-11 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 11:30 [PATCH] ext4: Don't claim block from group which has corrupt bitmap Aneesh Kumar K.V
2008-02-11 11:36 ` Aneesh Kumar K.V [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=20080211113652.GA3833@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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