From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: [CFT][PATCH] Re: fat problem in 2.4.2
Date: 1 Mar 2001 12:05:50 -0800 [thread overview]
Message-ID: <97ma2u$840$1@penguin.transmeta.com> (raw)
In-Reply-To: <E14YXft-0008GK-00@the-village.bc.nu> <Pine.GSO.4.21.0103011345110.11577-100000@weyl.math.psu.edu>
In article <Pine.GSO.4.21.0103011345110.11577-100000@weyl.math.psu.edu>,
Alexander Viro <viro@math.psu.edu> wrote:
>
>Alan, fix is really quite simple. Especially if you have vmtruncate()
>returning int (ac1 used to do it, I didn't check later ones). Actually
>just a generic_cont_expand() done on expanding path in vmtruncate()
>will be enough - it should be OK for all cases, including normal
>filesystems. <grabbing -ac7>
>
>OK, any brave soul to test that? All I can promise that it builds.
This looks like it would create a dummy block even for non-broken
filesystems (ie truncating a file to be larger on ext2 would create a
block, no?). While that would work, it would also waste disk-space.
Linus
next prev parent reply other threads:[~2001-03-01 20:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-25 20:08 fat problem in 2.4.2 James D Strandboge
2001-02-25 20:20 ` Alan Cox
2001-03-01 14:25 ` Peter Daum
2001-03-01 15:09 ` [PATCH] " Alexander Viro
2001-03-02 0:21 ` Albert D. Cahalan
2001-03-01 18:19 ` Alan Cox
2001-03-01 19:39 ` [CFT][PATCH] " Alexander Viro
2001-03-01 20:05 ` Linus Torvalds [this message]
2001-03-01 20:52 ` Chris Mason
2001-03-01 20:56 ` Roman Zippel
2001-03-01 21:07 ` Alexander Viro
2001-03-01 21:27 ` Roman Zippel
2001-03-02 7:45 ` ftruncate not extending files? bert hubert
2001-03-02 9:57 ` Malcolm Beattie
2001-03-02 10:56 ` Dmitry A. Fedorov
2001-03-02 14:15 ` Hugh Dickins
2001-03-03 19:32 ` Kai Henningsen
[not found] ` <mng==20010302095701.A4685@sable.ox.ac.uk>
2001-03-02 23:41 ` Jens-Uwe Mager
[not found] <200103012005.MAA08328@penguin.transmeta.com>
2001-03-01 20:24 ` [CFT][PATCH] Re: fat problem in 2.4.2 Alexander Viro
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='97ma2u$840$1@penguin.transmeta.com' \
--to=torvalds@transmeta.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