From: Ted Ts'o <tytso@mit.edu>
To: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] ext4 regression and bug fixes for 2.6.38
Date: Thu, 10 Feb 2011 19:02:54 -0500 [thread overview]
Message-ID: <20110211000254.GI16597@thunk.org> (raw)
In-Reply-To: <E1PmaYB-0001aV-RQ@tytso-glaptop>
On Mon, Feb 07, 2011 at 06:31:19PM -0500, Theodore Ts'o wrote:
> Hi Linus,
>
> Please pull from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git for_linus
>
> to get regression and bug fixes for 2.6.38.
>
> Thanks,
Hi Linus, it looks like you haven't pulled this tree yet. It turns
out there's one more patch (from Dan Carpenter) which I need to send
you, so I've updated for_linus branch with an additional commit. The
shortlog and diff should now be as shown below.
Please pull when you have a chance, thanks!!
- Ted
Curt Wohlgemuth (1):
ext4: Fix data corruption with multi-block writepages support
Dan Carpenter (1):
ext4: off by one check in ext4_groupinfo_create_slab()
Eric Sandeen (3):
ext4: fix panic on module unload when stopping lazyinit thread
ext4: make grpinfo slab cache names static
ext4: serialize unaligned asynchronous DIO
Lukas Czerner (1):
ext4: unregister features interface on module unload
Theodore Ts'o (2):
ext4: fix up ext4 error handling
jbd2: call __jbd2_log_start_commit with j_state_lock write locked
fs/ext4/ext4.h | 8 ++++
fs/ext4/extents.c | 10 +++--
fs/ext4/file.c | 60 +++++++++++++++++++++++++++++-
fs/ext4/mballoc.c | 100 +++++++++++++++++++++++++++++-------------------
fs/ext4/page-io.c | 36 +++++++++--------
fs/ext4/super.c | 66 ++++++++++++++++++++++----------
fs/jbd2/journal.c | 9 +++-
fs/jbd2/transaction.c | 21 +++++++---
8 files changed, 219 insertions(+), 91 deletions(-)
prev parent reply other threads:[~2011-02-11 0:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 23:31 [GIT PULL] ext4 regression and bug fixes for 2.6.38 Theodore Ts'o
2011-02-11 0:02 ` Ted Ts'o [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=20110211000254.GI16597@thunk.org \
--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;
as well as URLs for NNTP newsgroup(s).