> > > BTW, from where I sit, ocfs2 is "on hold" due to some additional work > > > which > > > hch identified when I was on vacation and not paying much attention. vma > > > walk, perhaps? > > > > I don't know of anything that should put it "on hold". Copying > > Mark on this. Mark? > > (cc hch) > > On 10 Aug Christoph told me "While OCFS is evolving really nicely there's a > bunch of major things that need to be sorted out". > > Christoph, could you please itemise these things?
Major items known: - oracore workarounds must go away - magic symlinks that pollute the posix filename namespace must go away - vma-walking locking must move to common code (zab is working on that afaik) - the buffered aio mess needs sorting out. imho the best thing was to just drop that code from ocfs for now and let oracle work with bcrl and suparna to make sure their buffered aio code works nicely with ocfs and/or picks up some of their ideas - there's still some procfs abuse That's just the off my head things, the oracle people actually asked me to wait with a review until they've cleared their TODO lists, I'll do a real review once I'll get some time. - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
