Re: If not readdir() then what?
- From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
- Date: Sun, 8 Apr 2007 01:44:34 +0200 (MEST)
On Apr 7 2007 16:36, Theodore Tso wrote:
So how do we solve this problem? I can think of two solutions:
1) Deprecate telldir/seekdir() altogether. Relatively few progams use
this functionality, and it is highly questionable how useful it is,
anyway. If you use telldir/seekdir and keep the cookie for a long
time, even the POSIX-provided guarantees about files that are created
and deleted between the telldir() and seekdir() points in time makes
its utility highly dubious.
2) If application programs must have telldir/seekdir, than expand the
size of the cookie from 32-bits to a minimum of 128 bits, and
preferably larger --- say 512 bits, to accomodate systems that might
be using 512-bit variant of SHA-2. [...]
Maybe a combination of both? That is, replace telldir by an
independent emulation layer.
Jan
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- If not readdir() then what?
- From: Ulrich Drepper
- Re: If not readdir() then what?
- From: Theodore Tso
- If not readdir() then what?
- Prev by Date: Re: [RFC][PATCH -mm] swsusp: Use rbtree for tracking allocated swap
- Next by Date: kernel oops with badly formatted module option
- Previous by thread: Re: If not readdir() then what?
- Next by thread: Re: If not readdir() then what?
- Index(es):
Relevant Pages
|
