All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustav Munkby <grddev@gmail.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Christoph Hellwig <hch@lst.de>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] hfsplus: read support for directory hardlinks
Date: Tue, 03 May 2011 16:11:31 +0200	[thread overview]
Message-ID: <4DC00D13.5060903@gmail.com> (raw)
In-Reply-To: <20110502124048.GL9487@ZenIV.linux.org.uk>

On 05/02/2011 02:40 PM, Al Viro wrote:
> What happens to rename() with that thing?  Specifically, what happens to
> loop detection?

Good point.

Since my main interest was retrieving contents of a backup, I did not much
consider the impact of write operations. Before the patch, the source files were
exposed as normal files, and the target directories as normal directories, so
one could easily have introduced loops with rename operations before.

In line with the read-only support, I would suggest to conservatively prevent
any rename where the source is a directory hardlink. I have prepared a patch
along those lines, but I cannot test it right now.

  reply	other threads:[~2011-05-03 14:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29 10:20 [PATCH] hfsplus: read support for directory hardlinks Gustav Munkby
2011-05-02  8:46 ` Christoph Hellwig
2011-05-02 12:40   ` Al Viro
2011-05-03 14:11     ` Gustav Munkby [this message]
2011-05-03 14:26       ` [PATCH] hfsplus: disable rename of " Gustav Munkby
2011-05-03 17:10         ` Andreas Dilger
2011-05-03 21:29           ` Gustav Munkby
2011-05-04  9:30       ` [PATCH] hfsplus: read support for " Christoph Hellwig
2011-05-04 15:04         ` Gustav Munkby
2011-05-19 11:09           ` Christoph Hellwig
2011-05-19 15:57             ` Gustav Munkby
2011-05-20 10:30               ` [PATCH v2] hfsplus: readonly " Gustav Munkby

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=4DC00D13.5060903@gmail.com \
    --to=grddev@gmail.com \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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.