search for: cachem

Mark and Joel, I found two serious bugs about xattr and inline-data. the first bug: in ocfs2_mknod(), we check and found the ACL or security xattr entry could be set into inode in ocfs2_calc_xattr_init(), then don't reserve block for them. But in ocfs2_mknod_locked(), if we found ocfs2 support inline-data, then set id_count with the max_inline_data. After that, we set acl/security xattr

...) [CRAN] 7: curl (4.3.2 -> 5.0.0 ) [CRAN] 8: Rcpp (1.0.7 -> 1.0.10) [CRAN] 9: ps (1.6.0 -> 1.7.4 ) [CRAN] 10: processx (3.5.2 -> 3.8.0 ) [CRAN] 11: purrr (0.3.4 -> 1.0.1 ) [CRAN] 12: magrittr (2.0.1 -> 2.0.3 ) [CRAN] 13: fastmap (1.1.0 -> 1.1.1 ) [CRAN] 14: cachem (1.0.6 -> 1.0.7 ) [CRAN] 15: fs (1.5.2 -> 1.6.1 ) [CRAN] Enter one or more numbers, or an empty line to skip updates: * installing *source* package 'nser' ... ** package 'nser' successfully unpacked and MD5 sums checked ** using staged installation ** R ** data *** mo...

...5.0.0 ) [CRAN] > 8: Rcpp (1.0.7 -> 1.0.10) [CRAN] > 9: ps (1.6.0 -> 1.7.4 ) [CRAN] > 10: processx (3.5.2 -> 3.8.0 ) [CRAN] > 11: purrr (0.3.4 -> 1.0.1 ) [CRAN] > 12: magrittr (2.0.1 -> 2.0.3 ) [CRAN] > 13: fastmap (1.1.0 -> 1.1.1 ) [CRAN] > 14: cachem (1.0.6 -> 1.0.7 ) [CRAN] > 15: fs (1.5.2 -> 1.6.1 ) [CRAN] > > Enter one or more numbers, or an empty line to skip updates: > * installing *source* package 'nser' ... > ** package 'nser' successfully unpacked and MD5 sums checked > ** using staged ins...

...ed 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...

In normal tree rotation left process, we will never touch the tree branch above subtree_index and ocfs2_extend_rotate_transaction doesn't reserve the credits for them either. But when we want to delete the rightmost extent block, we have to update the rightmost records for all the rightmost branch(See ocfs2_update_edge_lengths), so we have to allocate extra credits for them. What's more,

Hi Mark/Joel, These are 2 bug fix for b-tree. Please review. I have sent out the first one last week, but it was based on cacheme. So resend it. Now it bases on joel's fixes branch. The second one is another b-tree rotation bug. I guess the reason why we never meet with it is that no one has ever used b-tree like reflink before. ;) Regards, Tao

.... There are a lot of patches because this entire series is supposed to be isomorphic. No behavior is to change, just the flexibility of our API. Thus, each patch tries to be readily understandable. Thank you for your patience! [View] http://oss.oracle.com/git/?p=jlbec/linux-2.6.git;a=shortlog;h=cacheme [Pull] git://oss.oracle.com/git/jlbec/linux-2.6.git cacheme Joel Becker (40): ocfs2: Make the ocfs2_caching_info structure self-contained. ocfs2: Change metadata caching locks to an operations structure. ocfs2: Take the inode out of the metadata read/write paths. ocfs2: mo...