From: xaiki@sgi.com
To: xfs-dev@sgi.com
Cc: xfs@oss.sgi.com
Subject: Don't use d_alloc_anon for open_by_handle
Date: Fri, 2 May 2008 11:55:37 +1000 [thread overview]
Message-ID: <1209693339-4861-1-git-send-email-xaiki@sgi.com> (raw)
In-Reply-To: <20080501070244.GH108924158@sgi.com>
One of our DMAPI user found that in some cases inodes weren't getting through
xfs_inactive() in any reasonable amount of time. Investigation tracked it down
to the use of d_alloc_anon() combined with another thread accessing the same
inode via an open().
So we introduce a stripped down version of d_alloc_anon, that won't try to find
an existing dentry, nor will hash it.
next parent reply other threads:[~2008-05-02 2:08 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 ` xaiki [this message]
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
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=1209693339-4861-1-git-send-email-xaiki@sgi.com \
--to=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