From: Joel Becker <jlbec@evilplan.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mark Fasheh <mfasheh@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org
Subject: [GIT PULL] ocfs2 important fix for $next_version-rc1
Date: Fri, 27 May 2011 02:52:48 -0700 [thread overview]
Message-ID: <20110527095248.GD4966@noexit.corp.google.com> (raw)
In-Reply-To: <20110526094632.GB8252@noexit.corp.google.com>
Linus et al,
Mea culpa. The online defrag code in the ocfs2 feature pull had
a naked 64-bit divide that I missed in eyeballing and we all missed in
testing. None of us managed to build the sucker on 32bit in the past
two months. That's on me. Thank you to akpm for noticing. Also
included is a bugfix in the defrag location guessing.
I'd really like to get this in before -rc1 so that ocfs2 builds
aren't broken there. Please pull.
Mr Egg-on-his-face (Joel)
The following changes since commit a74b81b0aff4a01e0816df5915c854fb52c5e87f:
Merge branch 'linux-next' of git://git.kernel.org/pub/scm/linux/kernel/git/jlbec/ocfs2 (2011-05-26 10:55:15 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlbec/ocfs2.git linux-next
Joel Becker (1):
Merge branch 'move_extents' of git://oss.oracle.com/git/tye/linux-2.6 into ocfs2-merge-window
Tristan Ye (2):
Ocfs2/move_extents: Avoid doing division in extent moving.
Ocfs2/move_extents: Validate moving goal after the adjustment.
fs/ocfs2/move_extents.c | 41 ++++++++++++++++++++---------------------
1 files changed, 20 insertions(+), 21 deletions(-)
--
"Sometimes one pays most for the things one gets for nothing."
- Albert Einstein
http://www.jlbec.org/
jlbec@evilplan.org
prev parent reply other threads:[~2011-05-27 9:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 9:46 [GIT PULL] ocfs2 features for $next_version Joel Becker
2011-05-27 9:52 ` Joel Becker [this message]
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=20110527095248.GD4966@noexit.corp.google.com \
--to=jlbec@evilplan.org \
--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