Re: inode values in file system driver

From: Adrian McMenamin (adrian@mcmen.demon.co.uk)
Date: Wed May 14 2003 - 13:31:02 EST


On Tuesday 13 May 2003 15:56, Andreas Schwab wrote:
> Nikita Danilov <Nikita@Namesys.COM> writes:

> |> 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/



This archive was generated by hypermail 2b29 : Thu May 15 2003 - 22:00:53 EST