On Tue, Mar 20, 2012 at 03:27:12PM -0400, J. Bruce Fields wrote: > What are the chances of getting this reviewed for this merge cycle? Is > it on somebody's list? > > If it would make it any simpler: the one that I think absolutely must get wider > review, and get merged through Al's tree, is "vfs: take i_mutex on renamed > file". > > There aren't actually any dependencies between that and the rest; Based on discussion at LSF, and absent any objections, I'm leaving "vfs: take i_mutex on renamed file" for Al to take, and merging the rest through the nfsd tree for 3.5. (Al, assuming that's the correct thing to do, should I add an acked-by/reviewed-by for you to the patches I merge?) --b. > and > the rest is mainly in nfsd/ and locks.c (changes to which have mostly > been going through my tree anyway, I think); other than that: > > fs/attr.c | 3 ++ > fs/namei.c | 18 +++++++++++++- > > straightforward changes that tend to look like: > > + error = break_deleg(inode, O_WRONLY); > + if (error) > + return error; > > include/linux/fs.h | 19 +++++++++++++-- > > and some definitions. > > --b. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
