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 bug fixes for 3.6
Date: Fri, 17 Aug 2012 10:55:48 -0400 [thread overview]
Message-ID: <20120817145548.GA29433@thunk.org> (raw)
The following changes since commit 0d7614f09c1ebdbaa1599a5aba7593f147bf96ee:
Linux 3.6-rc1 (2012-08-02 16:38:10 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus_stable
for you to fetch changes up to 89a4e48f8479f8145eca9698f39fe188c982212f:
ext4: fix kernel BUG on large-scale rm -rf commands (2012-08-17 09:42:17 -0400)
----------------------------------------------------------------
The following are all bug fixes and regressions. The most notable are
the ones which cause problems for ext4 on RAID --- a performance
problem when mounting very large filesystems, and a kernel OOPS when
doing an rm -rf on large directory hierarchies on fast devices.
----------------------------------------------------------------
Theodore Ts'o (5):
ext4: make sure the journal sb is written in ext4_clear_journal_err()
ext4: avoid kmemcheck complaint from reading uninitialized memory
ext4: don't call ext4_error while block group is locked
ext4: fix long mount times on very big file systems
ext4: fix kernel BUG on large-scale rm -rf commands
fs/ext4/balloc.c | 62 +++++++++++++++++++++++++++++++---------------------
fs/ext4/bitmap.c | 1 -
fs/ext4/extents.c | 1 +
fs/ext4/super.c | 6 +++++
fs/jbd2/journal.c | 3 ++-
include/linux/jbd2.h | 1 +
6 files changed, 47 insertions(+), 27 deletions(-)
reply other threads:[~2012-08-17 14:55 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=20120817145548.GA29433@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 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).