From: Nikita Danilov <Nikita@Namesys.COM>
To: Jamie Lokier <jamie@shareable.org>
Cc: Andrew Morton <akpm@osdl.org>,
"Chen, Kenneth W" <kenneth.w.chen@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: posix_fallocate question again
Date: Thu, 21 Aug 2003 19:47:14 +0400 [thread overview]
Message-ID: <16196.59778.993371.804217@laputa.namesys.com> (raw)
In-Reply-To: <20030821153835.GA29245@mail.jlokier.co.uk>
Jamie Lokier writes:
> Nikita Danilov wrote:
> > fallocate() will be useful when writing into file through
> > mmap(). Currently kernel can just drop dirtied page at any moment (if
> > ->writepage() fails with -ENOSPC), so the only safe way to modify file
> > through mmap() is by using mlock().
>
> Isn't msync() reliable? I.e. will it at least report the error?
Seems latest 2.6 (19 Aug change sets by Andrew Morton) got support for
this: shrink_list() set AS_ENOSPC on mapping and error will later be
returned.
>
> -- Jamie
Nikita.
next prev parent reply other threads:[~2003-08-21 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 19:07 posix_fallocate question again Chen, Kenneth W
2003-08-20 19:53 ` Andrew Morton
2003-08-21 9:00 ` Nikita Danilov
2003-08-21 15:38 ` Jamie Lokier
2003-08-21 15:47 ` Nikita Danilov [this message]
2003-08-20 20:46 ` Christoph Hellwig
2003-08-21 2:36 ` Ulrich Drepper
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=16196.59778.993371.804217@laputa.namesys.com \
--to=nikita@namesys.com \
--cc=akpm@osdl.org \
--cc=jamie@shareable.org \
--cc=kenneth.w.chen@intel.com \
--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