linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: [GIT PULL] ext4 changes for 3.13
Date: Wed, 13 Nov 2013 19:32:15 -0500	[thread overview]
Message-ID: <20131114003215.GA31632@thunk.org> (raw)

The following changes since commit 61e6cfa80de5760bbe406f4e815b7739205754d2:

  Linux 3.12-rc5 (2013-10-13 15:41:28 -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 3f61c0cc706d5c0beee7af17ffeb706403cf513c:

  ext4: add prototypes for macro-generated functions (2013-11-11 22:40:40 -0500)

----------------------------------------------------------------
Ext4 updates for 3.13.  Mostly bug fixes and cleanups.

----------------------------------------------------------------
Andreas Dilger (2):
      ext4: return non-zero st_blocks for inline data
      ext4: add prototypes for macro-generated functions

Azat Khuzhin (1):
      ext4: drop set but otherwise unused variable from ext4_add_dirent_to_inline()

BoxiLiu (1):
      ext4: change ext4_read_inline_dir() to return 0 on success

Darrick J. Wong (1):
      ext4: don't count free clusters from a corrupt block group

Eric Sandeen (2):
      ext4: remove unreachable code in ext4_can_extents_be_merged()
      ext4: remove unreachable code after ext4_can_extents_be_merged()

Jan Kara (2):
      ext4: fix assertion in ext4_add_complete_io()
      ext4: fixup kerndoc annotation of mpage_map_and_submit_extent()

Lukas Czerner (1):
      ext4: fix FITRIM in no journal mode

Ming Lei (2):
      ext4: fix performance regression in ext4_writepages
      ext4: pair trace_ext4_writepages & trace_ext4_writepages_result

Theodore Ts'o (3):
      ext4: add ratelimiting to ext4 messages
      ext4: avoid bh leak in retry path of ext4_expand_extra_isize_ea()
      ext4: use prandom_u32() instead of get_random_bytes()

 fs/ext4/balloc.c  |  13 +++++-
 fs/ext4/ext4.h    |  17 +++++++
 fs/ext4/extents.c |  35 +-------------
 fs/ext4/ialloc.c  |   2 +-
 fs/ext4/inline.c  |   3 +-
 fs/ext4/inode.c   |  54 +++++++++++++---------
 fs/ext4/mballoc.c |   4 +-
 fs/ext4/mmp.c     |   2 +-
 fs/ext4/page-io.c |   5 +-
 fs/ext4/super.c   | 159 ++++++++++++++++++++++++++++++++++++++-------------------------
 fs/ext4/xattr.c   |   1 +
 11 files changed, 168 insertions(+), 127 deletions(-)

                 reply	other threads:[~2013-11-14  0:32 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=20131114003215.GA31632@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).