On Mon, Feb 22, 2010 at 03:35:51PM -0500, Valerie Aurora wrote: > The fact that may_open() could truncate a file gave me a lot of > heartburn when working on union mounts, so I was thrilled to see that > truncate handling has been moved out of may_open() in Al's for-next > tree. However, it seems to me that the surrounding elaborate > mnt_want_write() dance is no longer needed? If so, this also > simplifies Ogawa Hirofumi "Fix use-after-free of vfsmount by > mnt_drop_write()" patch. > > Against Al's for-next branch. Lightly tested, please review. Val, anything around do_filp_open() should be on top of #untested. The whole area gets rewritten there. -- 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
