From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] xattr fixes branch
Date: Thu, 23 Oct 2008 17:22:46 -0700 [thread overview]
Message-ID: <20081024002246.GF12751@mail.oracle.com> (raw)
Folks,
To keep track of what we want to upstream in the 2.6.28-rc
cycle, I've put together a branch called 'xattr-28' with almost all of
the patches merged. You can see it and pull it from my linux-2.6.git
repository.
View:
http://oss.oracle.com/git/?p=jlbec/linux-2.6.git;a=shortlog;h=xattr-28
Pull:
git://oss.oracle.com/git/jlbec/linux-2.6.git xattr-28
The branch contains the following changes:
Joel Becker (5):
ocfs2: Check xattr block signatures properly.
ocfs2: Don't return -EFAULT from a corrupt xattr entry.
ocfs2: Check errors from ocfs2_xattr_update_xattr_search()
ocfs2: Specify appropriate journal access for new xattr buckets.
ocfs2: Don't repeat ocfs2_xattr_block_find()
Tao Ma (1):
ocfs2: Remove unused ocfs2_restore_xattr_block().
Tiger Yang (4):
ocfs2: fix license in xattr
ocfs2: fix function declaration and definition in xattr
ocfs2: remove duplicate definition in xattr
ocfs2: add handler_map array bounds checking
These fixes and cleanups I think are candidates for 2.6.28-rc.
The last patch I'm waiting for is Tao's "ocfs2: Proper hash collision
handling in xattr bucket division." That's also a bugfix, and I think a
candidate for 2.6.28-rc. Once we get that nailed down, I think we're
good, and we'll send this stuff along upstream.
Tristan, I'd love it if you could test this branch to make sure
these fixes and cleanups didn't break anything.
Joel
--
"Egotist: a person more interested in himself than in me."
- Ambrose Bierce
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
next reply other threads:[~2008-10-24 0:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 0:22 Joel Becker [this message]
2008-10-24 0:57 ` [Ocfs2-devel] xattr fixes branch Tao Ma
2008-10-24 1:16 ` Joel Becker
2008-10-25 21:19 ` Mark Fasheh
2008-10-27 4:06 ` Joel Becker
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=20081024002246.GF12751@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=ocfs2-devel@oss.oracle.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.