On Mon, Aug 12, 2013 at 11:20:01PM +1000, Dave Chinner wrote: > From: Dave Chinner <dchinner@xxxxxxxxxx> > > O_TMPFILE support requires allocating an inode that is not attached to the > a current namespace - it's anonymous. The current inode allocation code runs > through xfs_create() which requires a parent inode and a name to be passed to > it. for O_TMPFILE, we do not have a parent inode or a name so we cannot use > the same calling conventions as xfs_create() to allocate a inode. Btw, O_TMPFILE does get a path passed, which the existing implementations treat as an invisible parent. I would suggest we follow that path for our allocation decisions for now. _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
