From: Andrea Arcangeli <andrea@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andrew Morton <akpm@digeo.com>,
chrisl@vmware.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: writepage return value check in vmscan.c
Date: Thu, 24 Oct 2002 13:44:55 +0200 [thread overview]
Message-ID: <20021024114455.GG3354@dualathlon.random> (raw)
In-Reply-To: <1035450906.8675.4.camel@irongate.swansea.linux.org.uk>
On Thu, Oct 24, 2002 at 10:15:06AM +0100, Alan Cox wrote:
> On Thu, 2002-10-24 at 09:36, Andrew Morton wrote:
> > A few fixes have been discussed. One way would be to allocate
> > the space for the page when it is first faulted into reality and
> > deliver SIGBUS if backing store for it could not be allocated.
>
> You still have to handle the situation where the page goes walkies and
> you get ENOSPC or any other ERANDOMSUPRISE from things like NFS. SIGBUS
> appears the right thing to do.
I would tend to agree SIGBUS could be the right thing to do since the
other (current) option is silent data corruption.
Andrea
next prev parent reply other threads:[~2002-10-24 11:38 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 8:25 writepage return value check in vmscan.c chrisl
2002-10-24 8:36 ` Andrew Morton
2002-10-24 9:15 ` Alan Cox
2002-10-24 11:44 ` Andrea Arcangeli [this message]
2002-10-24 16:12 ` Andrew Morton
2002-10-24 17:59 ` chrisl
2002-10-24 11:31 ` Andrea Arcangeli
2002-10-24 18:30 ` chrisl
2002-10-24 18:40 ` Andrea Arcangeli
2002-10-24 19:14 ` Rik van Riel
2002-10-24 19:25 ` Andrew Morton
2002-10-24 17:57 ` chrisl
2002-10-24 18:33 ` Andrea Arcangeli
2002-10-24 19:15 ` chrisl
2002-10-24 20:41 ` Andrea Arcangeli
2002-10-24 21:17 ` chrisl
2002-10-24 20:46 ` Andrew Morton
2002-10-24 21:23 ` chrisl
2002-10-24 21:29 ` Andrew Morton
2002-10-25 16:11 ` Paul Larson
2002-10-25 16:31 ` Christoph Hellwig
2002-10-25 17:07 ` Rik van Riel
2002-10-25 18:44 ` Andrew Morton
2002-10-28 19:17 ` chrisl
2002-10-28 19:53 ` Andrew Morton
2002-10-28 20:38 ` chrisl
2002-10-28 21:14 ` Andrea Arcangeli
2002-10-28 8:28 ` Christoph Rohland
2002-10-28 18:44 ` chrisl
2002-10-28 19:22 ` Andrea Arcangeli
2002-10-28 19:29 ` chrisl
2002-10-29 6:10 ` Randy.Dunlap
2002-10-29 7:08 ` Andreas Dilger
2002-10-28 19:58 ` chrisl
2002-10-28 21:32 ` Andrea Arcangeli
2002-10-30 4:13 ` chrisl
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=20021024114455.GG3354@dualathlon.random \
--to=andrea@suse.de \
--cc=akpm@digeo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chrisl@vmware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.