From: Peter Zijlstra <peterz@infradead.org>
To: Petr Tesarik <ptesarik@suse.cz>, Dave Chinner <dgc@sgi.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: mmap behavior on out-of-space conditions
Date: Thu, 02 Aug 2007 15:06:15 +0200 [thread overview]
Message-ID: <1186059975.12034.111.camel@twins> (raw)
In-Reply-To: <1186058486.2289.17.camel@elijah.suse.cz>
On Thu, 2007-08-02 at 14:41 +0200, Petr Tesarik wrote:
> Hello,
>
> while solving a different issue, my colleague Libor Pechacek found a
> problem with handling mmapped sparse files. If you mmap the hole insidea
> sparse file and write to it, the data gets silently lost if there is not
> enough space left on the underlying device.
I think Dave's block_page_mkwrite() stuff addresses this as well, no?
http://lkml.org/lkml/2007/3/18/198
Peter
next prev parent reply other threads:[~2007-08-02 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 12:41 mmap behavior on out-of-space conditions Petr Tesarik
2007-08-02 13:06 ` Peter Zijlstra [this message]
2007-08-02 13:18 ` Guillaume Chazarain
2007-08-02 18:52 ` Andrew Morton
2007-08-02 22:20 ` David Chinner
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=1186059975.12034.111.camel@twins \
--to=peterz@infradead.org \
--cc=dgc@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ptesarik@suse.cz \
/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