Re: [PATCH 5/6] clean up OCFS2 nlink handling
- From: Steven Whitehouse <swhiteho@xxxxxxxxxx>
- Date: Thu, 10 Aug 2006 09:07:32 +0100
Hi,
On Wed, 2006-08-09 at 12:15 -0700, Dave Hansen wrote:
On Wed, 2006-08-09 at 18:12 +0100, Christoph Hellwig wrote:[snip]
did you look whether gfs2 in -mm needs something similar?
It doesn't appear to. It doesn't manipulate i_nlink in the same, direct
manner.
-- Dave
I think it will need something similar. I suspect the required changes
will all be confined to routines in inode.c. If the link count is
changed by (a) remote node(s), then gfs2_inode_attr_in() might change
the link count. Also gfs2_change_nlink() is the other place to look. I
think everywhere else is ok,
Steve.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH 5/6] clean up OCFS2 nlink handling
- From: Dave Hansen
- Re: [PATCH 5/6] clean up OCFS2 nlink handling
- References:
- [PATCH 0/6] read-only bind mount prep work
- From: Dave Hansen
- [PATCH 5/6] clean up OCFS2 nlink handling
- From: Dave Hansen
- Re: [PATCH 5/6] clean up OCFS2 nlink handling
- From: Christoph Hellwig
- Re: [PATCH 5/6] clean up OCFS2 nlink handling
- From: Dave Hansen
- [PATCH 0/6] read-only bind mount prep work
- Prev by Date: Re: [PATCH] OMAP: I2C driver for TI OMAP boards #4
- Next by Date: [PATCH] fuse: fix error case in fuse_readpages
- Previous by thread: Re: [PATCH 5/6] clean up OCFS2 nlink handling
- Next by thread: Re: [PATCH 5/6] clean up OCFS2 nlink handling
- Index(es):
Relevant Pages
|
