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 update for 3.1-rc3
Date: Sun, 21 Aug 2011 00:45:54 -0400 [thread overview]
Message-ID: <E1Quzv0-0002pd-P2@tytso-glaptop> (raw)
Hi Linus,
These fix a number of bugs (some of them data corruptors) when a various
obscure or less commonly-used ext4 mount options/modes are enabled
(i.e., dioread_nolock, data=journal, nojournal mode).
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git for_linus
- Ted
Curt Wohlgemuth (1):
ext4: Fix ext4_should_writeback_data() for no-journal mode
Jiaying Zhang (2):
ext4: call ext4_ioend_wait and ext4_flush_completed_IO in ext4_evict_inode
ext4: flush any pending end_io requests before DIO reads w/dioread_nolock
Tao Ma (1):
ext4: Resolve the hang of direct i/o read in handling EXT4_IO_END_UNWRITTEN.
Theodore Ts'o (1):
ext4: fix nomblk_io_submit option so it correctly converts uninit blocks
fs/ext4/ext4_jbd2.h | 4 ++--
fs/ext4/indirect.c | 9 +++++++--
fs/ext4/inode.c | 26 ++++++++++++++++++++++++--
fs/ext4/page-io.c | 6 ++++--
fs/ext4/super.c | 1 -
5 files changed, 37 insertions(+), 9 deletions(-)
reply other threads:[~2011-08-21 4:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1Quzv0-0002pd-P2@tytso-glaptop \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox