All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Meyer <thomas@m3y3r.de>
To: Rob Landley <rob@landley.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Copy on write hard links?
Date: Wed, 25 Sep 2013 16:28:53 +0200	[thread overview]
Message-ID: <1380119333.7453.4.camel@localhost.localdomain> (raw)
In-Reply-To: <1380117572.1974.81@driftwood>

Am Mittwoch, den 25.09.2013, 08:59 -0500 schrieb Rob Landley:
> On 09/24/2013 01:36:56 PM, Thomas Meyer wrote:
> > Hi,
> > 
> > Is there such a thing?
> 
> In the kernel's vfs layer? 

Yes, that would be a nice feature!

> No, although some filesystems (ala btrfs) do  
> things like that with snapshots.
> 
> In userspace? Breaking hardlinks when updating a file is fairly normal,  
> that's why they distinguish between "truncate and rewrite" (preserve  
> hardlinks) and "write new file and rename over old file" (break  
> hardlinks, avoiding the more obvious race conditions).

so every user space application needs to implement that for itself?
I wonder how hard it would be to implement this on vfs layer? linkat()
with a new flag as api or something like that.

> 
> Rob



  reply	other threads:[~2013-09-25 14:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24 18:36 Copy on write hard links? Thomas Meyer
2013-09-25  1:40 ` Adam Borowski
2013-09-25 13:59 ` Rob Landley
2013-09-25 14:28   ` Thomas Meyer [this message]
2013-09-25 14:37     ` richard -rw- weinberger
2013-09-29  5:22       ` Pádraig Brady
2013-09-29  7:14         ` Richard Weinberger
2013-09-29 17:19           ` Pádraig Brady
2013-12-13 22:58     ` Jörn Engel

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=1380119333.7453.4.camel@localhost.localdomain \
    --to=thomas@m3y3r.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.