From: Michael Raskin <7c6f434c@mail.ru>
To: Edward Shishkin <edward.shishkin@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [BUG] fallocate behavior when crossing end-of-file
Date: Wed, 06 May 2009 19:12:04 +0400 [thread overview]
Message-ID: <4A01A8C4.20205@mail.ru> (raw)
In-Reply-To: <4A01A5DF.5050406@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Edward Shishkin wrote:
>> Desired: something (probably, one block) is allocated/reserved for the
>> file. File length is set to 1 byte.
>
> Where is it documented?
>
> IMHO we should only guarantee that writes
> to [0, 1] won't fail because of lack of disk space.
> Other things (including file size) are up to implementation.
POSIX, SUS.
http://www.opengroup.org/onlinepubs/009695399/functions/posix_fallocate.html
<<<
If the offset+ len is beyond the current file size, then
posix_fallocate() shall adjust the file size to offset+ len. Otherwise,
the file size shall not be changed.
>>>
Michael Raskin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQEcBAEBAgAGBQJKAajDAAoJEE6tnN0aWvw3umYH/Rhcs2m4UosPLOsSylVAiFiB
rRJbeYWX5xaw9wTCV7RW3BkAEM2gJ5De10j4x7g81L7GZQZNz3Pwu6WN+kQOrBnG
gSeCg7u5OpvJUrX6HxeJEeUOCg9VDzuTNyEWY3pUEo7L00MLuYqTQimg2pua3oAv
Ib7bUWVfRguxgQVO7pnw//CV6L+KBY7OP2za+c2x+Ec+KN0QsgAlYATxNP9+hI4o
VJL7nIGoAs5rZXkLuDJpQYgI2sl6yzZy1Jq0Q3+UnjDDLlU945yMQm4LGTEMMHJX
i/Ci58y+SNhiDFrPrW1nRCZXE0RiEk01hGTtVVI2yfZJz/dabZAtSgEbyp0k0/c=
=6Fmf
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2009-05-06 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 13:03 [BUG] fallocate behavior when crossing end-of-file Raskin Michael
2009-05-06 14:59 ` Edward Shishkin
2009-05-06 15:10 ` Chris Mason
2009-05-06 15:12 ` Michael Raskin [this message]
2009-05-06 15:36 ` Edward Shishkin
2009-05-06 21:07 ` Michael Raskin
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=4A01A8C4.20205@mail.ru \
--to=7c6f434c@mail.ru \
--cc=edward.shishkin@gmail.com \
--cc=linux-btrfs@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