From: "Theodore Ts'o" <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] ext4 bugfixes/cleanups
Date: Sat, 02 Aug 2008 21:47:52 -0400 [thread overview]
Message-ID: <E1KPShM-0007Ks-M0@closure.thunk.org> (raw)
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git for_linus
This patch series contains a number of bug fixes that have been
discovered by primarily by benchmarkers and people who have been trying
out ext4. A few cleanups have been included as well.
Thanks!!
- Ted
Aneesh Kumar K.V (5):
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
Eric Sandeen (4):
ext4: sync up block and inode bitmap reading functions
ext4: lock block groups when initializing
ext4: fix ext4_da_write_begin error path
ext4: remove write-only variables from ext4_ordered_write_end
Hidehiro Kawai (2):
ext4: don't read inode block if the buffer has a write error
jbd2: don't abort if flushing file data failed
Li Zefan (1):
ext4: improve ext4_fill_flex_info() a bit
Theodore Ts'o (6):
ext4: Allow read/only mounts with corrupted block group checksums
ext4: Fix ext4_ext_journal_restart()
ext4: Fix lack of credits BUG() when deleting a badly fragmented inode
ext4: don't assume extents can't cross block groups when truncating
ext4: Cleanup whitespace and other miscellaneous style issues
ext4: unexport jbd2_journal_update_superblock
next reply other threads:[~2008-08-03 1:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-03 1:47 Theodore Ts'o [this message]
2008-08-03 17:52 ` [GIT PULL] ext4 bugfixes/cleanups Linus Torvalds
2008-08-03 18:45 ` Theodore Tso
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=E1KPShM-0007Ks-M0@closure.thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.