| To: | David Chinner <dgc@xxxxxxx> |
|---|---|
| Subject: | Re: correct use of vmtruncate()? |
| From: | "Aneesh Kumar K.V" <aneesh.kumar@xxxxxxxxxxxxxxxxxx> |
| Date: | Wed, 30 Apr 2008 13:17:38 +0530 |
| Cc: | linux-fsdevel <linux-fsdevel@xxxxxxxxxxxxxxx>, linux-mm <linux-mm@xxxxxxxxx>, xfs-oss <xfs@xxxxxxxxxxx> |
| In-reply-to: | <20080429100601.GO108924158@sgi.com> |
| References: | <20080429100601.GO108924158@sgi.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.17+20080114 (2008-01-14) |
On Tue, Apr 29, 2008 at 08:06:01PM +1000, David Chinner wrote: > Folks, > > It appears to me that vmtruncate() is not used correctly in > block_write_begin() and friends. The short summary is that it > appears that the usage in these functions implies that vmtruncate() > should cause truncation of blocks on disk but no filesystem > appears to do this, nor does the documentation imply they should. Looking at ext*_truncate, I see we are freeing blocks as a part of vmtruncate. Or did I miss something ? -aneesh |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | TAKE 979416 - Include linux/random.h in all builds, David Chinner |
|---|---|
| Next by Date: | [PATCH] Fix current xfs build, Matthew Wilcox |
| Previous by Thread: | Re: correct use of vmtruncate()?, David Chinner |
| Next by Thread: | Re: correct use of vmtruncate()?, David Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |