All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@MIT.EDU>
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: Thu, 01 Aug 2013 01:28:46 -0400	[thread overview]
Message-ID: <nsx7gg6569d.fsf@lambda.thunk.org> (raw)


The following changes since commit 3b2f64d00c46e1e4e9bd0bb9bb12619adac27a4b:

  Linux 3.11-rc2 (2013-07-21 12:05:29 -0700)

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 44fb851dfb2f8e3462617e19a7b3b9025db9d919:

  ext4: add WARN_ON to check the length of allocated blocks (2013-07-29 12:51:42 -0400)

----------------------------------------------------------------
ext4 bugfixes for v3.11-rc4

----------------------------------------------------------------
Eric Sandeen (1):
      ext4: destroy ext4_es_cachep on module unload

Theodore Ts'o (2):
      ext4: make sure group number is bumped after a inode allocation race
      ext4: fix retry handling in ext4_ext_truncate()

Zheng Liu (1):
      ext4: add WARN_ON to check the length of allocated blocks

 fs/ext4/extents.c |  2 +-
 fs/ext4/ialloc.c  | 10 +++++-----
 fs/ext4/inode.c   | 39 ++++++++++++++++++---------------------
 fs/ext4/super.c   |  1 +
 4 files changed, 25 insertions(+), 27 deletions(-)

             reply	other threads:[~2013-08-01  5:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-01  5:28 Theodore Ts'o, Theodore Ts'o [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-08-01  5:35 [GIT PULL] more ext4 bug fixes Theodore Ts'o, Theodore Ts'o
2013-08-01  4:45 Theodore Ts'o
2013-07-20  0:29 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=nsx7gg6569d.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.