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
Date: Mon, 15 Jul 2013 00:42:44 -0400 [thread overview]
Message-ID: <nsxhafwv3gb.fsf@lambda.thunk.org> (raw)
The following changes since commit 6ae06ff51eab5dcbbf959b05ce0f11003a305ba5:
ext4: optimize starting extent in ext4_ext_rm_leaf() (2013-07-01 08:12:41 -0400)
are available in the git repository at:
http://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus
for you to fetch changes up to e7676a704ee0a1ef71a6b23760b5a8f6896cb1a1:
ext4: don't allow ext4_free_blocks() to fail due to ENOMEM (2013-07-13 00:40:35 -0400)
----------------------------------------------------------------
Various regression and bug fixes for ext4.
----------------------------------------------------------------
Anatol Pomozov (1):
ext4: rate limit printk in buffer_io_error()
Jan Kara (2):
ext4: silence warning in ext4_writepages()
ext4: fix warning in ext4_evict_inode()
Theodore Ts'o (4):
ext4: fix ext4_get_group_number()
ext4: don't show usrquota/grpquota twice in /proc/mounts
ext4: fix spelling errors and a comment in extent_status tree
ext4: don't allow ext4_free_blocks() to fail due to ENOMEM
fs/ext4/balloc.c | 4 ++--
fs/ext4/extents_status.c | 22 ++++++++++------------
fs/ext4/inode.c | 12 ++++++------
fs/ext4/mballoc.c | 11 ++++++++---
fs/ext4/page-io.c | 35 +++++++++++++++++++++--------------
fs/ext4/super.c | 14 ++++----------
6 files changed, 51 insertions(+), 47 deletions(-)
next reply other threads:[~2013-07-15 4:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 4:42 Theodore Ts'o [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-22 14:30 [GIT PULL] ext4 bug fixes Theodore Ts'o
2008-08-23 23:44 ` Christoph Hellwig
2008-08-24 1:05 ` 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=nsxhafwv3gb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox