From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Mingming Cao <cmm@us.ibm.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Patches for patch queue
Date: Tue, 19 Aug 2008 12:08:34 +0530 [thread overview]
Message-ID: <20080819063834.GB6516@skywalker> (raw)
Hi Mingming,
Some update for patches in the patch queue. I am sending it as a diff
against patch queue so that it makes it easier to apply
The first hunk is a missed return 0 as a part of patch
ext4_invalidate_pages_when_delalloc_alloc_fail.patch
diff --git a/ext4_invalidate_pages_when_delalloc_alloc_fail.patch b/ext4_invalidate_pages_when_delalloc_alloc_fail.patch
index f0722ab..d47d3bf 100644
--- a/ext4_invalidate_pages_when_delalloc_alloc_fail.patch
+++ b/ext4_invalidate_pages_when_delalloc_alloc_fail.patch
@@ -92,7 +92,7 @@ Index: linux-2.6.27-rc3/fs/ext4/inode.c
+ * will find the dirty page again
+ */
+ if (err == -EAGAIN)
-+ return;
++ return 0;
+ /*
+ * get block failure will cause us
+ * to loop in writepages. Because
diff --git a/fix-delalloc-release-block-reservation-for-truncate b/fix-delalloc-release-block-reservation-for-truncate
index 8dc891b..32f1063 100644
--- a/fix-delalloc-release-block-reservation-for-truncate
+++ b/fix-delalloc-release-block-reservation-for-truncate
@@ -48,8 +48,8 @@ Index: linux-2.6.27-rc3/fs/ext4/inode.c
+ * but since this function is called from invalidate
+ * page, it's harmless to return without any action
+ */
-+ printk(KERN_INFO "ext4 delalloc try to release %d reserved"
-+ "blocks for inode %lu, but there is no reserved"
++ printk(KERN_INFO "ext4 delalloc try to release %d reserved "
++ "blocks for inode %lu, but there is no reserved "
+ "data blocks\n", to_free, inode->i_ino);
+ spin_unlock(&EXT4_I(inode)->i_block_reservation_lock);
+ return;
next reply other threads:[~2008-08-19 6:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 6:38 Aneesh Kumar K.V [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-16 7:18 Patches for patch queue Aneesh Kumar K.V
2007-08-16 15:45 ` Dave Kleikamp
2007-08-20 15:21 ` Dave Kleikamp
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=20080819063834.GB6516@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox