From: Chris Mason <mason@suse.com>
To: Alexander Viro <viro@math.psu.edu>, Oleg Drokin <green@namesys.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
marcelo@conectiva.com.br, linux-kernel@vger.kernel.org,
reiserfs-dev@namesys.com
Subject: Re: [reiserfs-dev] Re: [PATCH] expanding truncate
Date: Fri, 04 Jan 2002 12:33:32 -0500 [thread overview]
Message-ID: <18370000.1010165612@tiny> (raw)
In-Reply-To: <Pine.GSO.4.21.0201031111130.23312-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0201031111130.23312-100000@weyl.math.psu.edu>
On Thursday, January 03, 2002 11:17:56 AM -0500 Alexander Viro
<viro@math.psu.edu> wrote:
[ expanding truncate patch ]
>
> Seriously, it looks like a half-arsed and very old attempt to do common
> expanding truncate() for no-holes filesystems. BTW, these days rlimit
> checks are done by vmtruncate().
Whoops, good point. It was a very old and half-arsed attempt at doing
expanding truncate to no-holes filesystems (mostly the fat flavors).
reiserfs likes it because it needs to insert zero'd out indirect items for
holes.
I've got the bits to make fat use it too, the only real gain being able to
save staroffice files onto fat.
<email backlog disclaimer, ignore if already dealt with>
-chris
next prev parent reply other threads:[~2002-01-04 17:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-03 7:21 [PATCH] expanding truncate Oleg Drokin
2002-01-03 7:50 ` Andrew Morton
2002-01-03 12:25 ` Alan Cox
2002-01-03 12:25 ` Oleg Drokin
2002-01-03 16:17 ` Alexander Viro
2002-01-04 17:33 ` Chris Mason [this message]
2002-01-11 20:52 ` [reiserfs-dev] " Chris Mason
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=18370000.1010165612@tiny \
--to=mason@suse.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=reiserfs-dev@namesys.com \
--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