From: Joel Becker <boel.becker@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mark Fasheh <mfasheh@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [GIT PULL] Important ocfs2 fix for 2.6.37-rc1
Date: Sun, 14 Nov 2010 01:31:37 -0800 [thread overview]
Message-ID: <20101114093136.GA27747@mail.oracle.com> (raw)
Linus, et al,
We've got a rather large problem in our cluster locking in the
2.6.37-rc1 changes. Tao has found the problem (a signed-vs-unsigned
error that I should have caught). Here's the fix.
Please pull.
Joel
The following changes since commit 2d3b07c07b39c4b7d9b6641052a02d996cd5d87c:
Merge branch 'x86-platform-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip (2010-10-28 12:25:42 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlbec/ocfs2.git upstream-linus
Tao Ma (1):
ocfs2: Change some lock status member in ocfs2_lock_res to char.
fs/ocfs2/ocfs2.h | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
reply other threads:[~2010-11-14 9:31 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=20101114093136.GA27747@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=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).