LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
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 update
Date: Sun, 10 Feb 2008 01:33:11 -0500	[thread overview]
Message-ID: <E1JO5kV-0005WX-JJ@closure.thunk.org> (raw)

Hi Linus,

Please pull from:

        git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git for_linus

These are mostly bug fixes that we've found since the last pull request.
The one non-bugfix change is that I've added a sanity check to assure
that production ext3 filesystems don't get mounted with ext4dev
accidentally.  The need for this was discovered when Eric Sandeen
started putting ext4 into Fedora's Rawhide release for initial testing.

Thanks,

						- Ted

Aneesh Kumar K.V (5):
      jbd2: Fix reference counting on the journal commit block's buffer head
      JBD2: Use the incompat macro for testing the incompat feature.
      ext4: Fix null bh pointer dereference in mballoc
      ext4: Fix circular locking dependency with migrate and rm.
      ext4: Don't panic in case of corrupt bitmap

Dave Kleikamp (1):
      JBD2:  Clear buffer_ordered flag for barried IO request on success

Eric Sandeen (2):
      allow in-inode EAs on ext4 root inode
      ext4: allocate struct ext4_allocation_context from a kmem cache

Jan Kara (2):
      jbd: Remove useless loop when writing commit record
      ext4: Fix Direct I/O locking

Mingming Cao (1):
      jbd2: Add error check to journal_wait_on_commit_record to avoid oops

Theodore Tso (1):
      ext4: Add new "development flag" to the ext4 filesystem

Valerie Clement (1):
      ext4: Don't set EXTENTS_FL flag for fast symlinks

 fs/ext4/inode.c         |  115 +++++++++++++++-----------------
 fs/ext4/mballoc.c       |  164 ++++++++++++++++++++++++++++++-----------------
 fs/ext4/migrate.c       |  123 +++++++++++++++++++++++------------
 fs/ext4/namei.c         |    1 +
 fs/ext4/super.c         |   11 +++
 fs/jbd/commit.c         |   14 ++--
 fs/jbd2/commit.c        |   10 ++-
 fs/jbd2/recovery.c      |    2 +-
 include/linux/ext4_fs.h |    7 ++
 9 files changed, 270 insertions(+), 177 deletions(-)


             reply	other threads:[~2008-02-10  6:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-10  6:33 Theodore Ts'o [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-30  2:45 [GIT PULL] ext4 update Theodore Ts'o
2008-02-25 22:47 Theodore Ts'o
2008-01-29  5:50 Theodore Ts'o
2008-01-29 12:53 ` Theodore Tso
2008-01-29 21:54   ` Jan Engelhardt
2008-01-30  7:11     ` Theodore Tso
2008-01-30  8:38       ` Paul Collins
2008-01-30  8:52       ` Linus Torvalds
2007-10-17  4:26 Theodore Ts'o
2007-10-17  4:51 ` david
2007-10-18  6:29   ` Andreas Dilger
2007-10-17 15:59 ` Linus Torvalds
2007-10-17 22:55   ` Theodore Tso
2007-10-25 23:31   ` Andrew Morton
2007-10-25 23:44     ` Linus Torvalds
2007-10-25 23:53       ` Andrew Morton
2007-07-18 13:42 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=E1JO5kV-0005WX-JJ@closure.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).