public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joel Becker <boel.becker@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mark Fasheh <mfasheh@suse.com>,
	tao.ma@oracle.com, Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: [GIT PULL] ocfs2 fixes for 2.6.36.
Date: Tue, 7 Sep 2010 16:41:14 -0700	[thread overview]
Message-ID: <20100907234114.GD21935@mail.oracle.com> (raw)

Linus et al,
	Here are the ocfs2 fixes we have ready for pulling right now.  I
have a bit of a procedural question, though.  I've been busy, so Tao was
kind enough to take the fixes I already had and apply all the new fixes.
He coordinated testing them and getting them ready to go upstream.
That's why I have his git tree in the pull request below.
	I wasn't sure how the signoffs work for this.  He's got signoffs
on the stuff he put together, because it's coming through his tree.  My
naive assumption is that this is the correct way to go.  If you'd like
another arrangement (same branch in my tree, a merge commit somewhere to
stick my SoB on, etc), let me know.
	Otherwise, please pull.

Joel


The following changes since commit 2bfc96a127bc1cc94d26bfaa40159966064f9c8c:
  Linus Torvalds (1):
        Linux 2.6.36-rc3

are available in the git repository at:

  git://oss.oracle.com/git/tma/linux-2.6.git fixes

Jan Kara (2):
      ocfs2: Flush drive's caches on fdatasync
      ocfs2: Fix deadlock when allocating page

Mark Fasheh (6):
      ocfs2: properly set and use inode group alloc hint
      ocfs2: split out inode alloc code from ocfs2_mknod_locked
      ocfs2: use ocfs2_alloc_dinode_update_counts() instead of open coding
      ocfs2: allow return of new inode block location before allocation of the inode
      ocfs2: split out ocfs2_prepare_orphan_dir() into locking and prep functions
      ocfs2: Fix orphan add in ocfs2_create_inode_in_orphan

Sunil Mushran (2):
      ocfs2: Fix metaecc error messages
      ocfs2: Fix incorrect checksum validation error

Tao Ma (2):
      ocfs2: make __ocfs2_page_mkwrite handle file end properly.
      ocfs2: Use the right group in nfs sync check.

Tristan Ye (1):
      Ocfs2: Fix a regression bug from mainline commit(6b933c8e6f1a2f3118082c455eef25f9b1ac7b45).

 fs/ocfs2/alloc.c        |    2 +-
 fs/ocfs2/blockcheck.c   |    4 +-
 fs/ocfs2/file.c         |   15 ++-
 fs/ocfs2/inode.c        |    6 +-
 fs/ocfs2/mmap.c         |    8 +-
 fs/ocfs2/namei.c        |  302 ++++++++++++++++++++++++++++++++++++-----------
 fs/ocfs2/refcounttree.c |    5 +-
 fs/ocfs2/suballoc.c     |  219 ++++++++++++++++++++++++++++++----
 fs/ocfs2/suballoc.h     |   21 ++++
 9 files changed, 475 insertions(+), 107 deletions(-)

             reply	other threads:[~2010-09-07 23:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-07 23:41 Joel Becker [this message]
2010-09-08  2:19 ` [GIT PULL] ocfs2 fixes for 2.6.36 Linus Torvalds
2010-09-08  6:48   ` Tao Ma

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=20100907234114.GD21935@mail.oracle.com \
    --to=boel.becker@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfasheh@suse.com \
    --cc=ocfs2-devel@oss.oracle.com \
    --cc=tao.ma@oracle.com \
    --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