Hey everyone, We're coming up on the next merge window, and I only have a couple tiny fixes for ocfs2. I thought I'd list up what I know is outstanding, and I was hoping to find out if I was missing anything. If I am, I need to get it in linux-next and set for the merge window ASAP. - metaecc-stats This is a trivial patch I put together to track errors seen by the blockcheck code. No one has reviewed it. Not a high priority, but I suspect that if it looks good to a reviewer, we can push it whenever we want. - cacheme These are the changes that separate out the metadata cache from the ocfs2_inode. All metadata I/O and caching is done against the cache rather than a specific inode. This is needed for the refcount tree code. The code was ready for the 2.6.30 merge window, but we aren't going to push it until refcount trees are ready. - refcount Support for refcount trees in the filesystem. The basic code is quite hashed out. Tao's done a great job, and Tristan is beating on it. We're now tracking down major bugs. It's not quite organized for mainline submission, and it really warrants some time in linux-next before we push it, so it won't be making the 2.6.31 merge window. I'm expecting 2.6.32 though. - reflink The generic reflink system call patch seems to have evolved as needed. I'm ready to push it upstream, but I don't think it goes without some consumer. That is, I push it with the refcount tree code. I'm open to dissenters, though, and I'm going to be asking VFS people about it. That's what I have. What'd I miss? Joel -- "Gone to plant a weeping willow On the bank's green edge it will roll, roll, roll. Sing a lulaby beside the waters. Lovers come and go, the river roll, roll, rolls." Joel Becker Principal Software Developer Oracle E-mail: joel.becker at oracle.com Phone: (650) 506-8127
Joel Becker wrote:> Hey everyone, > We're coming up on the next merge window, and I only have a > couple tiny fixes for ocfs2. I thought I'd list up what I know is > outstanding, and I was hoping to find out if I was missing anything. If > I am, I need to get it in linux-next and set for the merge window ASAP. > > - metaecc-stats > This is a trivial patch I put together to track errors seen by the > blockcheck code. No one has reviewed it. Not a high priority, but I > suspect that if it looks good to a reviewer, we can push it whenever we > want.I thought I had sob-bed it. Anycase, sob for the following: http://git.kernel.org/?p=linux/kernel/git/jlbec/ocfs2.git;a=commitdiff;h=652005955cff547d2a845d5a794ba36e65550774> - cacheme > These are the changes that separate out the metadata cache from the > ocfs2_inode. All metadata I/O and caching is done against the cache > rather than a specific inode. This is needed for the refcount tree > code. The code was ready for the 2.6.30 merge window, but we aren't > going to push it until refcount trees are ready. > > - refcount > Support for refcount trees in the filesystem. The basic code is > quite hashed out. Tao's done a great job, and Tristan is beating on it. > We're now tracking down major bugs. It's not quite organized for > mainline submission, and it really warrants some time in linux-next > before we push it, so it won't be making the 2.6.31 merge window. I'm > expecting 2.6.32 though. > > - reflink > The generic reflink system call patch seems to have evolved as > needed. I'm ready to push it upstream, but I don't think it goes > without some consumer. That is, I push it with the refcount tree code. > I'm open to dissenters, though, and I'm going to be asking VFS people > about it. > > That's what I have. What'd I miss?It probably would be best to hold-off on reflink till 2.6.32. I can't think of anything else. This will be the fewest number of patches we've pushed during merge window since... ever.
Hi, On Mon 01-06-09 18:06:36, Joel Becker wrote:> We're coming up on the next merge window, and I only have a > couple tiny fixes for ocfs2. I thought I'd list up what I know is > outstanding, and I was hoping to find out if I was missing anything. If > I am, I need to get it in linux-next and set for the merge window ASAP.I've just sent off a patch series that may be worth merging for 2.6.31... It contains some quota fixes and lockdep support for cluster locks. Honza -- Jan Kara <jack at suse.cz> SUSE Labs, CR
On Mon, Jun 01, 2009 at 06:06:36PM -0700, Joel Becker wrote:> We're coming up on the next merge window, and I only have a > couple tiny fixes for ocfs2. I thought I'd list up what I know is > outstanding, and I was hoping to find out if I was missing anything. If > I am, I need to get it in linux-next and set for the merge window ASAP.I've now created the merge-window branch for the 2.6.31 cycle. It contains the quota fixes, the orphan dir background scan, metaecc stats, and a few small fixes. The only thing I see outstanding is the btree add branch bug Tao and Mark are working on. Please have a look and let me know if there are any problems or if anything is missing. Joel [Pull] git://git.kernel.org/pub/scm/linux/kernel/git/jlbec/ocfs2.git merge-window [View] http://git.kernel.org/?p=linux/kernel/git/jlbec/ocfs2.git;a=shortlog;h=merge-window -- Life's Little Instruction Book #510 "Count your blessings." Joel Becker Principal Software Developer Oracle E-mail: joel.becker at oracle.com Phone: (650) 506-8127
Apparently Analagous Threads
- [PATCH V3] ocfs2: xattr: fix inlined xattr reflink
- [PATCH 1/2] ocfs2: Delay inode update transactions after verifying the input flags
- Patches that adds delayed orphan scan timer (rev 3)
- [PATCH] ocfs2: Update VFS inode's id info after reflink.
- [RFC] The reflink(2) system call.