From: andros@netapp.com
To: bhalevy@panasas.com
Cc: linux-nfs@vger.kernel.org, Andy Adamson <andros@netapp.com>
Subject: [PATCH 3/5] SQUASHME pnfs-submit: remove pnfs_destroy_inode
Date: Tue, 6 Jul 2010 17:17:00 -0400 [thread overview]
Message-ID: <1278451022-2889-4-git-send-email-andros@netapp.com> (raw)
In-Reply-To: <1278451022-2889-3-git-send-email-andros@netapp.com>
From: Andy Adamson <andros@netapp.com>
Move WARN_ONs and list check into pnfs_layout_destroy under the i_lock
Signed-off-by: Andy Adamson <andros@netapp.com>
---
fs/nfs/inode.c | 18 +-----------------
fs/nfs/pnfs.c | 9 +++++++++
fs/nfs/pnfs.h | 4 ++++
3 files changed, 14 insertions(+), 17 deletions(-)
diff --git a/fs/nfs/inode.c b/fs/nfs/inode.c
index fa310b1..229cdab 100644
--- a/fs/nfs/inode.c
+++ b/fs/nfs/inode.c
@@ -1379,27 +1379,11 @@ struct inode *nfs_alloc_inode(struct super_block *sb)
return &nfsi->vfs_inode;
}
-static void pnfs_destroy_inode(struct nfs_inode *nfsi)
-{
-#ifdef CONFIG_NFS_V4_1
- if (!list_empty(&nfsi->layout.segs))
- pnfs_destroy_layout(nfsi);
-
- WARN_ON(!list_empty(&nfsi->layout.segs));
- if (nfsi->layout.refcount)
- printk("%s: WARNING: layout.refcount %d\n", __func__,
- nfsi->layout.refcount);
- WARN_ON(nfsi->layout.refcount);
- WARN_ON(!list_empty(&nfsi->layout.lo_layouts));
- WARN_ON(nfsi->layout.ld_data);
-#endif /* CONFIG_NFS_V4_1 */
-}
-
void nfs_destroy_inode(struct inode *inode)
{
struct nfs_inode *nfsi = NFS_I(inode);
- pnfs_destroy_inode(nfsi);
+ pnfs_destroy_layout(nfsi);
kmem_cache_free(nfs_inode_cachep, nfsi);
}
diff --git a/fs/nfs/pnfs.c b/fs/nfs/pnfs.c
index baa3de7..fb9374b 100644
--- a/fs/nfs/pnfs.c
+++ b/fs/nfs/pnfs.c
@@ -379,6 +379,15 @@ pnfs_destroy_layout(struct nfs_inode *nfsi)
lo = grab_current_layout(nfsi);
if (lo) {
pnfs_free_layout(lo, &range);
+ WARN_ON(!list_empty(&nfsi->layout.segs));
+ WARN_ON(!list_empty(&nfsi->layout.lo_layouts));
+ WARN_ON(nfsi->layout.ld_data);
+
+ if (nfsi->layout.refcount != 1)
+ printk(KERN_WARNING "%s: layout refcount not=1 %d\n",
+ __func__, nfsi->layout.refcount);
+ WARN_ON(nfsi->layout.refcount != 1);
+
put_layout(lo);
}
spin_unlock(&nfsi->vfs_inode.i_lock);
diff --git a/fs/nfs/pnfs.h b/fs/nfs/pnfs.h
index c60eff6..9b0fed4 100644
--- a/fs/nfs/pnfs.h
+++ b/fs/nfs/pnfs.h
@@ -190,6 +190,10 @@ static inline void pnfs_update_layout(struct inode *ino,
#else /* CONFIG_NFS_V4_1 */
+static inline void pnfs_destroy_layout(struct nfs_inode *nfsi)
+{
+}
+
static inline void get_lseg(struct pnfs_layout_segment *lseg)
{
}
--
1.6.6
next prev parent reply other threads:[~2010-07-06 20:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 21:16 [PATCH 0/5] cleanup inode.c and bug fixes andros
2010-07-06 21:16 ` [PATCH 1/5] SQUASHME pnfs-submit: remove pnfs_init_once andros
2010-07-06 21:16 ` [PATCH 2/5] SQUASHME pnfs-submit remove pnfs_alloc_init_inode andros
2010-07-06 21:17 ` andros [this message]
2010-07-06 21:17 ` [PATCH 4/5] SQUASHME pnfs-submit: set layoutcommit status after async error handler andros
2010-07-06 21:17 ` [PATCH 5/5] SQUASHME pnfs-submit: set layoutget " andros
2010-07-07 9:27 ` [PATCH 2/5] SQUASHME pnfs-submit remove pnfs_alloc_init_inode Boaz Harrosh
2010-07-07 17:03 ` William A. (Andy) Adamson
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=1278451022-2889-4-git-send-email-andros@netapp.com \
--to=andros@netapp.com \
--cc=bhalevy@panasas.com \
--cc=linux-nfs@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