Re: [PATCH] eCryptfs: Delay writing 0's after llseek until write

On Mon, May 21, 2007 at 09:07:08PM -0700, Andrew Morton wrote:
> On Mon, 21 May 2007 18:00:21 -0500 Michael Halcrow <[email protected]> wrote:
> 
> > Delay writing 0's out in eCryptfs after a seek past the end of the
> > file until data is actually written.
> 
> a) why?

http://www.opengroup.org/onlinepubs/009695399/functions/lseek.html

``The lseek() function shall not, by itself, extend the size of a
file.''

> b) what is the impact upon a user of them not having this patch?

Applications that lseek() past the end of the file without writing
will experience unexpected behavior.

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

---

• Follow-Ups:
  • Re: [PATCH] eCryptfs: Delay writing 0's after llseek until write
    • From: "Nish Aravamudan" <[email protected]>

• References:
  • [PATCH] eCryptfs: Delay writing 0's after llseek until write
    • From: Michael Halcrow <[email protected]>
  • Re: [PATCH] eCryptfs: Delay writing 0's after llseek until write
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: [1/5] 2.6.22-rc2: known regressions
• Next by Date: Re: RFC: kconfig select warnings bogus?
• Previous by thread: Re: [PATCH] eCryptfs: Delay writing 0's after llseek until write
• Next by thread: Re: [PATCH] eCryptfs: Delay writing 0's after llseek until write
• 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]