From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Landley Subject: Re: [RFC] sys_punchhole() Date: Wed, 16 Nov 2005 06:08:18 -0600 References: <1131664994.25354.36.camel@localhost.localdomain> <20051110153254.5dde61c5.akpm@osdl.org> <200511110925.48259.ioe-lkml@rameria.de> In-Reply-To: <200511110925.48259.ioe-lkml@rameria.de> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511160608.18413.rob@landley.net> Sender: owner-linux-mm@kvack.org Return-Path: To: Ingo Oeser Cc: linux-kernel@vger.kernel.org, Andrew Morton , Badari Pulavarty , andrea@suse.de, hugh@veritas.com, linux-mm@kvack.org List-ID: On Friday 11 November 2005 02:25, Ingo Oeser wrote: > Hi, > > On Friday 11 November 2005 00:32, Andrew Morton wrote: > > Badari Pulavarty wrote: > > > We discussed this in madvise(REMOVE) thread - to add support > > > for sys_punchhole(fd, offset, len) to complete the functionality > > > (in the future). You know, if you wanted to get really really gross and disgusting about this, you could always have write(fd, NULL, count) punch a hole in the file. (Then have libc's write() check for NULL and error out, and have a seprate punch() call that does the write with the null...) Just one way to avoid introducing a new syscall... Rob -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org