> |> In other words, readdir(3) will not return dirent for inode with ino 0.
>
> I stand corrected. I was thinking of getdirentries, which does not have
> this problem. But this is traditional Unix behaviour.
>
OK. I've worked round this in my driver. It will now list the file, and does
so with inode 0 (I have not tinkered with anything outside my driver, so this
won't have any impact on any other fs). Is this A Bad Thing?
Adrian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/