+ return apply_root_dentry_ntfs(dentry, vol, w);
+ /* NTFS filename namespaces need careful consideration. A name for a
+ * NTFS file may be in either the POSIX, Win32, DOS, or Win32+DOS
+ * namespaces. The following list of assumptions and facts clarify the
+ * way that WIM dentries are mapped to NTFS files. The statements
+ * marked ASSUMPTION are statements I am assuming to be true due to the
+ * lack of documentation; they are verified in verify_dentry() and
+ * verify_inode() in verify.c.
+ *
+ * - ASSUMPTION: The root WIM dentry has neither a "long name" nor a
+ * "short name".
+ *
+ * - ASSUMPTION: Every WIM dentry other than the root directory provides
+ * a non-empty "long name" and a possibly empty "short name". The
+ * "short name" corresponds to the DOS name of the file, while the
+ * "long name" may be Win32 or POSIX.
+ *
+ * XXX It may actually be legal to have a short name but no long name
+ *
+ * - FACT: If a dentry has a "long name" but no "short name", then it is
+ * ambigious whether the name is POSIX or Win32+DOS, unless the name
+ * is a valid POSIX name but not a valid Win32+DOS name. wimlib
+ * currently will always create POSIX names for these files, as this
+ * is the behavior of the ntfs_create() and ntfs_link() functions.
+ *
+ * - FACT: Multiple WIM dentries may correspond to the same underlying
+ * inode, as provided at this point in the code by the d_inode member.
+ */