public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC] sys_punchhole()
Date: Sat, 12 Nov 2005 22:11:30 -0800 (PST)	[thread overview]
Message-ID: <dl6lei$aq5$1@terminus.zytor.com> (raw)
In-Reply-To: 1131686314.2833.0.camel@laptopd505.fenrus.org

Followup to:  <1131686314.2833.0.camel@laptopd505.fenrus.org>
By author:    Arjan van de Ven <arjan@infradead.org>
In newsgroup: linux.dev.kernel
> On Thu, 2005-11-10 at 15:23 -0800, 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).
> 
> in the past always this was said to be "really hard" in linux locking
> wise, esp. the locking with respect to truncate...
> 
> did you find a solution to this problem ?

For the sake of completeness, it should probably be stated that the
utility of such a function is pretty clear.

	-hpa

  reply	other threads:[~2005-11-13  6:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-10 23:23 [RFC] sys_punchhole() Badari Pulavarty
2005-11-10 23:32 ` Andrew Morton
2005-11-10 23:41   ` Badari Pulavarty
2005-11-10 23:55     ` Anton Altaparmakov
2005-11-11  8:25   ` Ingo Oeser
2005-11-11 19:07     ` Christoph Lameter
2005-11-16 12:08     ` Rob Landley
2005-11-16 12:20       ` Andrea Arcangeli
2005-11-13 15:09   ` Pavel Machek
2005-11-16 22:01     ` Badari Pulavarty
2005-11-16 23:37       ` Ric Wheeler
2005-11-21  6:46       ` Rob Landley
2005-11-18 16:42     ` Ragnar Kjørstad
2005-11-18 16:54       ` Badari Pulavarty
2005-11-11  5:18 ` Arjan van de Ven
2005-11-13  6:11   ` H. Peter Anvin [this message]
2005-11-16 16:05   ` Badari Pulavarty
2005-11-16 16:38     ` Anton Altaparmakov

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='dl6lei$aq5$1@terminus.zytor.com' \
    --to=hpa@zytor.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