All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: "Michael L. Semon" <mlsemon35@gmail.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: Multi-CPU harmless lockdep on x86 while copying data
Date: Tue, 11 Mar 2014 09:48:16 -0700	[thread overview]
Message-ID: <20140311164816.GA15676@infradead.org> (raw)
In-Reply-To: <20140310205118.GX6851@dastard>

On Tue, Mar 11, 2014 at 07:51:18AM +1100, Dave Chinner wrote:
> Yeah, b) seems like the way to simplify it - the filestreams code
> really only needs to track the parent/ag relationship rather than
> the child/parent relationship if there is a reliable way of
> determining the parent from the child.
> 
> What do we do with hardlinked files in this case? I'm happy to say
> "too bad" for these files mainly because the filestream allocator is
> aimed at associating multiple file creations together, so hard links
> really don't matter AFAICT...

We could flatly refuse filesystems for files with i_nlink > 1, or just
grab the first parent we get at.  Refusing seems like the better
alternative to me.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-03-11 16:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-09  2:58 Multi-CPU harmless lockdep on x86 while copying data Michael L. Semon
2014-03-10  2:55 ` Dave Chinner
2014-03-10 10:37   ` Christoph Hellwig
2014-03-10 11:12     ` Christoph Hellwig
2014-03-10 20:51       ` Dave Chinner
2014-03-11 16:48         ` Christoph Hellwig [this message]
2014-03-10 20:46     ` Dave Chinner
2014-03-10 21:16       ` Ben Myers
2014-03-10 21:24         ` Dave Chinner
2014-03-10 22:10           ` Ben Myers
2014-03-10 20:52   ` Ben Myers
2014-03-10 21:20     ` Dave Chinner
2014-03-10 21:30       ` Ben Myers

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=20140311164816.GA15676@infradead.org \
    --to=hch@infradead.org \
    --cc=david@fromorbit.com \
    --cc=mlsemon35@gmail.com \
    --cc=xfs@oss.sgi.com \
    /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.