From: "Josef 'Jeff' Sipek" <jsipek@cs.sunysb.edu>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: akpm@linux-foundation.org, Erez Zadok <ezk@cs.sunysb.edu>,
"Josef 'Jeff' Sipek" <jsipek@cs.sunysb.edu>
Subject: [PATCH 5/5] Unionfs: Remove unnecessary BUG_ON in unionfs_follow_link
Date: Fri, 29 Jun 2007 03:26:21 -0400 [thread overview]
Message-ID: <11831019822222-git-send-email-jsipek@cs.sunysb.edu> (raw)
In-Reply-To: <1183101981740-git-send-email-jsipek@cs.sunysb.edu>
From: Erez Zadok <ezk@cs.sunysb.edu>
Signed-off-by: Erez Zadok <ezk@cs.sunysb.edu>
Signed-off-by: Josef 'Jeff' Sipek <jsipek@cs.sunysb.edu>
---
fs/unionfs/inode.c | 30 ++++++++----------------------
1 files changed, 8 insertions(+), 22 deletions(-)
diff --git a/fs/unionfs/inode.c b/fs/unionfs/inode.c
index a86da5b..b5f9022 100644
--- a/fs/unionfs/inode.c
+++ b/fs/unionfs/inode.c
@@ -832,35 +832,21 @@ out:
}
/*
- * Check if dentry is valid or not, as per our generation numbers.
- * @dentry: dentry to check.
- * Returns 1 (valid) or 0 (invalid/stale).
+ * unionfs_follow_link takes a dentry, but it is simple. It only needs to
+ * allocate some memory and then call our ->readlink method. Our
+ * unionfs_readlink *does* lock our dentry and revalidate the dentry.
+ * Therefore, we do not have to lock our dentry here, to prevent a deadlock;
+ * nor do we need to revalidate it either. It is safe to not lock our
+ * dentry here, nor revalidate it, because unionfs_follow_link does not do
+ * anything (prior to calling ->readlink) which could become inconsistent
+ * due to branch management.
*/
-static inline int is_valid_dentry(struct dentry *dentry)
-{
- BUG_ON(!UNIONFS_D(dentry));
- BUG_ON(!UNIONFS_SB(dentry->d_sb));
- return (atomic_read(&UNIONFS_D(dentry)->generation) ==
- atomic_read(&UNIONFS_SB(dentry->d_sb)->generation));
-}
-
-/* We don't lock the dentry here, because readlink does the heavy lifting. */
static void *unionfs_follow_link(struct dentry *dentry, struct nameidata *nd)
{
char *buf;
int len = PAGE_SIZE, err;
mm_segment_t old_fs;
- /*
- * FIXME: Really nasty...we can get called from two distinct places:
- * 1) read_link - locks the dentry
- * 2) VFS lookup code - does NOT lock the dentry
- *
- * The proper thing would be to call dentry revalidate. It however
- * expects a locked dentry, and we can't cleanly guarantee that.
- */
- BUG_ON(!is_valid_dentry(dentry));
-
unionfs_read_lock(dentry->d_sb);
/* This is freed by the put_link method assuming a successful call. */
--
1.5.2.2.238.g7cbf2f2
prev parent reply other threads:[~2007-06-29 7:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 7:26 [GIT PULL -mm] Unionfs cleanups and fixes Josef 'Jeff' Sipek
2007-06-29 7:26 ` [PATCH 1/5] Unionfs: Convert all instances of "hidden" to "lower" Josef 'Jeff' Sipek
2007-06-29 7:26 ` [PATCH 2/5] Unionfs: Add missing unlock call in unionfs_file_release Josef 'Jeff' Sipek
2007-06-29 7:26 ` [PATCH 3/5] Unionfs: Use file->f_path instead of file->f_dentry Josef 'Jeff' Sipek
2007-06-29 7:26 ` [PATCH 4/5] Unionfs: Clarification comment for unionfs_lookup Josef 'Jeff' Sipek
2007-06-29 7:26 ` Josef 'Jeff' Sipek [this message]
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=11831019822222-git-send-email-jsipek@cs.sunysb.edu \
--to=jsipek@cs.sunysb.edu \
--cc=akpm@linux-foundation.org \
--cc=ezk@cs.sunysb.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).