public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Banks <gnb@melbourne.sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Niv Sardi <xaiki@sgi.com>, xfs-dev@sgi.com, xfs@oss.sgi.com, gnb@sgi.com
Subject: Re: Don't use d_alloc_anon for open_by_handle
Date: Mon, 05 May 2008 13:51:00 -0700	[thread overview]
Message-ID: <481F7334.8000408@melbourne.sgi.com> (raw)
In-Reply-To: <20080505184424.GA25933@infradead.org>

Christoph Hellwig wrote:
> On Mon, May 05, 2008 at 05:53:16AM -0400, Christoph Hellwig wrote:
>   
>> It shouldn't be slow.  You'd do the equivalent no_subtree check export
>> without parent fh, so what we do is call the fh_to_dentry method
>> and then call find_acceptable_alias to check if there's already an
>> dentry around and if yes use that one.  That latter part is what should
>> fix your problem.  If you want to be lazy you could just copy
>> find_acceptable_alias into the xfs code and call it directly and let me
>> clean up the mess later..
>>     
>
> Sorry, this was written before my cup of tea in the morning.
> find_acceptable_alias is of course a no-op in the no_subtree_check case,
> and thus it's identical to what we're currently doing in the handle
> code.  So any problem you see here will also be seen in an nfs
> environment with no_subtree_check, which is the sensible choise 
Agreed.
> and
> I think even the default these days.
I believe so.  We also use that as default on our shipping NAS servers
anyway.
>   So we'd better fix the lacking
> expiry in the core code. 
Mmm, sounds like fun.
>  Cc'ing Greg as he's been fighting this code
> quite a bit in the past.
>
>   
Thanks.  I'm on xfs-dev now so I've been lurking while you guys
discussed this :-)

-- 
Greg Banks, P.Engineer, SGI Australian Software Group.
The cake is *not* a lie.
I don't speak for SGI.

  reply	other threads:[~2008-05-05 20:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080501070244.GH108924158@sgi.com>
2008-05-02  1:55 ` Don't use d_alloc_anon for open_by_handle xaiki
2008-05-02  1:55   ` [PATCH] Don't use hashed dentries when doing open_by_handle xaiki
2008-05-02  1:55     ` [PATCH] Use xfs_d_alloc_anon for DM rdwr using handle code xaiki
2008-05-02  6:06   ` Don't use d_alloc_anon for open_by_handle Christoph Hellwig
2008-05-05  6:33     ` Niv Sardi
2008-05-05  9:53       ` Christoph Hellwig
2008-05-05 18:44         ` Christoph Hellwig
2008-05-05 20:51           ` Greg Banks [this message]
2008-05-06  1:38           ` Niv Sardi

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=481F7334.8000408@melbourne.sgi.com \
    --to=gnb@melbourne.sgi.com \
    --cc=gnb@sgi.com \
    --cc=hch@infradead.org \
    --cc=xaiki@sgi.com \
    --cc=xfs-dev@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox