From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Mingming Cao <cmm@us.ibm.com>, Theodore Tso <tytso@mit.edu>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Patches for the patchqueue
Date: Thu, 5 Jun 2008 15:20:32 +0530 [thread overview]
Message-ID: <20080605095032.GE8942@skywalker> (raw)
Hi Mingming,
These are the patches for patch queue. They have been sent to the
mailing list before. I am attaching them below so that it can be easily
pushed to the patch queue. The patches will be sent as a follow up to
this mail.
I modified the delalloc-clear-bh-delay-bit-fix.patch
to address only the VFS bug. The delay bit is properly cleared in
0001-delalloc-enospc.patch. I guess we should also push
003-delalloc-clear-bh-delay-bit-fix.patch to the stable series as
it is a VFS bug in handling delay buffer.
002-blkcleanup.patch patch can be merged with
ext4-use-inode-preallocation-with-noextents.patch. I am just posting it
as a separate patch so that others can review the changes.
The series file looks like
+ ext4-use-inode-preallocation-with-noextents.patch
+ 002-blkcleanup.patch
+ ext4-call-blkdev_issue_flush-on-fsync.patch
+ ext4-mb-add-ext4_has_free_blocks-check.patch
......
+ jbd2-Remove-data-ordered-mode-support-using-jbd-buf.patch
+ delalloc-vfs.patch
+ 003-delalloc-clear-bh-delay-bit-fix.patch
+ ext4-fix-fs-corruption-with-delalloc.patch
.....
+ percpucounter-add-sum-and-set-function.patch
+ 0001-delalloc-enospc.patch
+ jbd-blocks-reservation-fix-for-large-blk.patch
+ jbd2-blocks-reservation-fix-for-large-blk.patch
-aneesh
next reply other threads:[~2008-06-05 9:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 9:50 Aneesh Kumar K.V [this message]
2008-06-05 9:51 ` Patches for the patchqueue Aneesh Kumar K.V
2008-06-05 9:53 ` Aneesh Kumar K.V
2008-06-05 9:55 ` Aneesh Kumar K.V
2008-06-05 18:02 ` Mingming Cao
2008-06-05 18:59 ` Aneesh Kumar K.V
2008-06-05 18:51 ` Andreas Dilger
-- strict thread matches above, loose matches on Subject: below --
2008-06-06 18:24 Aneesh Kumar K.V
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=20080605095032.GE8942@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