From: Theodore Tso <tytso@mit.edu>
To: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: New ext4 patchset: 2.6.26-git6-ext4-2 // and 2.6.26-ext4-4
Date: Sun, 27 Jul 2008 21:21:10 -0400 [thread overview]
Message-ID: <20080728012110.GC9378@mit.edu> (raw)
In-Reply-To: <E1KMv2C-0007fs-1b@closure.thunk.org>
I've released a new patchset for post-2.6.26-git4 kernels (when Linus
accepted a set of patches for the 2.6.27-rc1 merge window). This
removes a problematic patch and adds a documentation patch to remind
people that when installing e2fsprogs 1.41.x, it's important to make
sure to update their /etc/mke2fs.conf file.
As a git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git 2.6.26-git6-ext4-2
http://git.kernel.org/?p=linux/kernel/git/tytso/ext4.git;a=shortlog;h=2.6.26-git6-ext4-2
As a patchset:
ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/2.6.26-git6-ext4-2
I've also updated the patch set vs. the 2.6.26-stock kernel, which can
be found here:
ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/2.6.26-ext4-4
- Ted
Akira Fujita (7):
ext4: online defrag-- Main function of defrag and ioctl implementation
ext4: online defrag-- Allocate new contiguous blocks with mballoc
ext4: online defrag-- Read and write file data with memory page
ext4: online defrag-- Exchange the blocks between two inodes
ext4: online defrag-- Defragmentation for the relevant files (-r mode)
ext4: online defrag-- Check the free space fragmentation (-f mode)
ext4: online defrag-- Move victim files for the target file (-f mode)
Aneesh Kumar K.V (6):
* ext4: Fix data corruption when writing to prealloc area
* ext4: Improve error handling in mballoc
* ext4: Convert the usage of NR_CPUS to nr_cpu_ids.
* ext4: Don't allow lg prealloc list to be grow large.
* ext4: Cleanup the block reservation code path
* ext4: undo the stable boundary patch changes
Eric Sandeen (3):
* sync up block & inode bitmap reading functions
* lock block groups when initializing
* Hook ext4 to the vfs fiemap interface.
Hidehiro Kawai (1):
* ext4: don't read inode block if the buffer has a write error
Josef Bacik (1):
Any block based fs (this patch includes ext3) just has to declare its own
Li Zefan (1):
* ext4: improve ext4_fill_flex_info() a bit
Theodore Ts'o (8):
* ext4: Allow read/only mounts with corrupted block group checksums
* jbd2: don't abort if flushing file data failed
* ext4: Cleanup whitespace and other miscellaneous style issues
* ext4: unexport jbd2_journal_update_superblock
* ext4: Update documentation to remind users to update mke2fs.conf
ext4: Stable/Unstable boundary
Basic vfs-level fiemap infrastructure, which sets up a new ->fiemap
Plug ocfs2 into ->fiemap. Some portions of ocfs2_get_clusters() had to be
prev parent reply other threads:[~2008-07-28 1:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-27 1:26 New ext4 patchset: 2.6.26-git6-ext4-1 // and 2.6.26-ext4-3 Theodore Ts'o
2008-07-27 2:39 ` Grant Coady
2008-07-27 12:33 ` Theodore Tso
2008-07-28 1:21 ` Theodore Tso [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=20080728012110.GC9378@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@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