Re: Support for SEEK_HOLE and SEEK_DATA for sparse files on lseek(2)

On Sun, Jun 18, 2006 at 04:14:11PM +0100, Al Viro wrote:

> Well...  Description makes sense and it isn't hard to implement.
> About the only question is about semantics for directories...

Why not claim it's undefined for now and -EINVAL if someone tries to
use it?  We can relax that at a later stage is someone comes up with a
well-thought out alternative after some discussion.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Support for SEEK_HOLE and SEEK_DATA for sparse files on lseek(2)
    • From: "André Goddard Rosa" <[email protected]>
  • Re: Support for SEEK_HOLE and SEEK_DATA for sparse files on lseek(2)
    • From: Al Viro <[email protected]>

• Prev by Date: Re: [patch 2/3] vdso: improve print_fatal_signals support by adding memory maps
• Next by Date: Re: [RFC][PATCH 20/20] honor r/w changes at do_remount() time
• Previous by thread: Re: Support for SEEK_HOLE and SEEK_DATA for sparse files on lseek(2)
• Next by thread: [RFC] New MMC driver model
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]