> On Wed, Aug 08, 2007 at 07:16:23PM +0200, Andreas Gruenbacher wrote: > > Split up struct nameidata into struct vfs_lookup with the lookup result > > and intent and the remaining fields for performing an actual lookup. > > Looks good as a start, but please don't put a struct path in there, > as the vfsmount will go away from the lookup intent as soon as we have > a new inode operation for atomic create + open, and not having it in the > struct path will make that removal a lot less painfull.
Btw, is the atomic open/create/truncate operation any further than conceptual phase? Have we worked out what to do with the ugly "create follows symlink" case? I'm just about to add another hack to the VFS to enable atomic open+truncate for fuse, and have a feeling that it will provoke some not so positive reactions ;) Miklos - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
