From: Kasper Dupont <kasperd@daimi.au.dk>
To: Alexander Viro <viro@math.psu.edu>
Cc: "Peter Chubb" <peter@chubb.wattle.id.au>,
Elladan <elladan@eskimo.com>,
" Jakob Østergaard" <jakob@unthought.net>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] ext2 and ext3 block reservations can be bypassed
Date: Mon, 13 May 2002 06:22:42 +0200 [thread overview]
Message-ID: <3CDF3F92.B3C3A18A@daimi.au.dk> (raw)
In-Reply-To: <Pine.GSO.4.21.0205121848080.27629-100000@weyl.math.psu.edu>
Alexander Viro wrote:
>
> On Mon, 13 May 2002, Peter Chubb wrote:
>
> > This is why in SVr4, struct cred is cloned at open time, and passed
> > down to each VFS operation.
>
> That doesn't work for shared mappings over holes. Unfortunately.
> Yes, credentials cache a-la 4.4BSD would help in many cases, but
> we have no reasonably credentials when kswapd writes a dirty page
> on disk. It _can_ cause allocations. And many processes might've
> touched that page until it finally got written out - which credentials
> would you use?
I'd rather have the check done when the page gets dirty in the
first place. Refuse the CoW if there is not diskspace to write
it back. Right now we can go beyond the diskspace we are allowed
to use and we will silently loose data if we go beyond the
available diskspace.
--
Kasper Dupont -- der bruger for meget tid på usenet.
For sending spam use mailto:razor-report@daimi.au.dk
next prev parent reply other threads:[~2002-05-13 4:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <791836807@toto.iv>
2002-05-12 22:04 ` [RFC] ext2 and ext3 block reservations can be bypassed Peter Chubb
2002-05-12 22:53 ` Alexander Viro
2002-05-13 4:22 ` Kasper Dupont [this message]
2002-05-13 4:51 ` Elladan
2002-05-14 19:29 Jesse Pollard
-- strict thread matches above, loose matches on Subject: below --
2002-05-14 18:54 Jesse Pollard
2002-05-14 19:04 ` Alexander Viro
2002-05-14 19:55 ` Mark Mielke
2002-05-14 18:07 Jesse Pollard
2002-05-14 18:00 Jesse Pollard
2002-05-14 17:53 Jesse Pollard
2002-05-14 18:23 ` Mark Mielke
2002-05-14 19:11 ` Alexander Viro
2002-05-12 16:23 Kasper Dupont
2002-05-12 16:42 ` Jakob Østergaard
2002-05-12 17:34 ` Elladan
2002-05-12 18:15 ` Alexander Viro
2002-05-12 18:37 ` Elladan
2002-05-12 19:02 ` Jakob Østergaard
2002-05-12 19:04 ` Mark Mielke
2002-05-13 17:09 ` Horst von Brand
2002-05-13 17:52 ` Elladan
2002-05-13 17:57 ` Christoph Hellwig
2002-05-14 16:22 ` Elladan
2002-05-14 16:55 ` Mark Mielke
2002-05-14 17:47 ` Elladan
2002-05-14 18:51 ` Kasper Dupont
2002-05-15 19:48 ` Pavel Machek
2002-05-15 20:29 ` Alan Cox
2002-05-14 15:40 ` Kasper Dupont
2002-05-14 15:56 ` Mark Mielke
2002-05-14 18:25 ` Kasper Dupont
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=3CDF3F92.B3C3A18A@daimi.au.dk \
--to=kasperd@daimi.au.dk \
--cc=elladan@eskimo.com \
--cc=jakob@unthought.net \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@chubb.wattle.id.au \
--cc=viro@math.psu.edu \
/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