On Wednesday February 6, rohde@xxxxxxx wrote:
> > > + dotdot.d_name.name = "..";
> > > + dotdot.d_name.len = 2;
> > > +
> > > + lock_kernel();
> > > + if (!udf_find_entry(child->d_inode, &dotdot, &fibh, &cfi))
> > > + goto out_unlock;
> > Have you ever tried this? I think this could never work. UDF doesn't have
> > entry named .. in a directory. You have to search for an entry that has
> > in fileCharacteristics set bit FID_FILE_CHAR_PARENT. Maybe you could
> > hack-around udf_find_entry() to recognize .. dentry and do the search
> > accordingly.
> Probably not. I just tested that I could read files and navigate the
> directory structure. However looking into UDF I think you are right - it
> will fail.
> I have extended udf_find_entry() to do an explicit check based on
> fileCharacteristics as you propose.
> How do I actually test this case?
- Mount the filesystem from the server.
- 'cd' a few directories down into the filesystem.
- reboot the server(1)
- on the client 'ls -l'.
(1) A full reboot isn't needed. Just unexport, unmount, remount,
re-export on the server.
alternately, use a non-linux client and cd down into the filesystem
and
ls -l ..
NeilBrown
-
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
