From: Michael Halcrow <mhalcrow@us.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] eCryptfs: Delay writing 0's after llseek until write
Date: Tue, 22 May 2007 09:51:25 -0500 [thread overview]
Message-ID: <20070522145124.GA3616@us.ibm.com> (raw)
In-Reply-To: <20070521210708.67d365dc.akpm@linux-foundation.org>
On Mon, May 21, 2007 at 09:07:08PM -0700, Andrew Morton wrote:
> On Mon, 21 May 2007 18:00:21 -0500 Michael Halcrow <mhalcrow@us.ibm.com> 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
next prev parent reply other threads:[~2007-05-22 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 23:00 [PATCH] eCryptfs: Delay writing 0's after llseek until write Michael Halcrow
2007-05-22 4:07 ` Andrew Morton
2007-05-22 14:51 ` Michael Halcrow [this message]
2007-05-22 15:01 ` Nish Aravamudan
2007-05-22 16:41 ` Zach Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070522145124.GA3616@us.ibm.com \
--to=mhalcrow@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox