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] more ext4 bug fixes
Date: Fri, 19 Jul 2013 20:29:24 -0400 [thread overview]
Message-ID: <nsxy592axaz.fsf@lambda.thunk.org> (raw)
The following changes since commit e7676a704ee0a1ef71a6b23760b5a8f6896cb1a1:
ext4: don't allow ext4_free_blocks() to fail due to ENOMEM (2013-07-13 00:40:35 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus
for you to fetch changes up to 63b999685cb372e24eb73f255cd73547026370fd:
ext4: call ext4_es_lru_add() after handling cache miss (2013-07-16 10:28:47 -0400)
----------------------------------------------------------------
Fixes for 3.11-rc2, sent at 5pm, in the professoinal style. :-)
----------------------------------------------------------------
Theodore Ts'o (5):
ext4: fix error handling in ext4_ext_truncate()
ext4: simplify calculation of blocks to free on error
ext4: make the extent_status code more robust against ENOMEM failures
ext4: yield during large unlinks
ext4: call ext4_es_lru_add() after handling cache miss
fs/ext4/extents.c | 23 +++++++++++++++++++----
fs/ext4/extents_status.c | 51 +++++++++++++++++++++++++++++++++++++++------------
fs/ext4/inode.c | 7 ++-----
3 files changed, 60 insertions(+), 21 deletions(-)
next reply other threads:[~2013-07-20 0:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-20 0:29 Theodore Ts'o [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-01 4:45 [GIT PULL] more ext4 bug fixes Theodore Ts'o
2013-08-01 5:28 Theodore Ts'o, Theodore Ts'o
2013-08-01 5:35 Theodore Ts'o, Theodore Ts'o
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=nsxy592axaz.fsf@lambda.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.