From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: cmm@us.ibm.com, akpm@linux-foundation.org, adilger@clusterfs.com,
linux-ext4@vger.kernel.org
Subject: Re: [Take 2] ext2/3/4 block bitmap validation patches
Date: Mon, 19 Nov 2007 21:15:24 +0530 [thread overview]
Message-ID: <4741AF94.8010704@linux.vnet.ibm.com> (raw)
In-Reply-To: <1195484161-14472-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
Aneesh Kumar K.V wrote:
> This is the updated ext2/3/4 block bitmap validation patches
>
> Changes from the last post
>
> a) moved the bh_uptodate_or_lock and bh_submit_read to
> fs/buffer.c and added EXPORT_SYMBOL
>
> b) Updated bh_submit_read not to release buffer on
> failure. This handles one reference handling bug in the
> error patch.
>
>
I forgot to pass --numbered to git format-patch
The order is
[PATCH 1/4] Add buffer head related helper functions
[PATCH 2/4] ext2: add block bitmap validation
[PATCH 3/4] ext3: add block bitmap validation
[PATCH 4/4] ext4: add block bitmap validation
it is against patch queue and applies as the last set of
patches in the stable series
....
buffer_head_helper.patch
ext2_bitmap_validation.patch
ext3_bitmap_validation.patch
ext4_bitmap_validation.patch
stable-boundary
-aneesh
prev parent reply other threads:[~2007-11-19 15:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 14:55 [Take 2] ext2/3/4 block bitmap validation patches Aneesh Kumar K.V
2007-11-19 14:55 ` [PATCH] Add buffer head related helper functions Aneesh Kumar K.V
2007-11-19 14:55 ` [PATCH] ext2: add block bitmap validation Aneesh Kumar K.V
2007-11-19 14:56 ` [PATCH] ext3: " Aneesh Kumar K.V
2007-11-19 14:56 ` [PATCH] ext4: " Aneesh Kumar K.V
2007-11-21 21:43 ` Andreas Dilger
2007-11-19 15:45 ` 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=4741AF94.8010704@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=adilger@clusterfs.com \
--cc=akpm@linux-foundation.org \
--cc=cmm@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.