Message-ID: <3F0F1586.5090005@inet.com>
Date: Fri, 11 Jul 2003 14:52:38 -0500
From: Eli Carter <eli.carter@inet.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
MIME-Version: 1.0
To: linux-kernel@vger.kernel.org
Subject: .truncate function in filesystems
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1186
Lines: 27

All,

I'm rather at a loss to understand what .truncate is supposed to do when 
it _extends_ a file (2.5.68+ kernel).  Looking through the examples in 
the tree, I don't see where they deal with that case.  Could someone 
give me a clue as to how .truncate is supposed to...tell the kernel what 
blocks it is to use when it goes to read from the extended portion of 
the file?

So far, I have googled, grep'ed, looked at lwn.net, started in on 
linux.bkbits.net, emailed linux-fsdevel and kernel-newbies...  and I'm 
still not getting anywhere.  Even a basic explanation of how filesystems 
  deal/interact with buffer heads and inodes would probably help at this 
point.

Any clues or pointers or _anything_ would be very much appreciated. :/

Eli
--------------------. "If it ain't broke now,
Eli Carter           \                  it will be soon." -- crypto-gram
eli.carter(a)inet.com `-------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/