Re: Need of inode->i_mutex in xfs

xfs

Re: Need of inode->i_mutex in xfs_write()

To:	kanishk rastogi <kanishk.85@xxxxxxxxx>
Subject:	Re: Need of inode->i_mutex in xfs_write()
From:	David Chinner <dgc@xxxxxxx>
Date:	Fri, 24 Aug 2007 08:51:11 +1000
Cc:	xfs@xxxxxxxxxxx
In-reply-to:	<9ee2fe770708210826n5952e727od0df16a5a7b267f0@xxxxxxxxxxxxxx>
References:	<9ee2fe770708210826n5952e727od0df16a5a7b267f0@xxxxxxxxxxxxxx>
Sender:	xfs-bounce@xxxxxxxxxxx
User-agent:	Mutt/1.4.2.1i

On Tue, Aug 21, 2007 at 09:11:56PM +0545, kanishk rastogi wrote:
> I was looking at the xfs_write code path in kernel 2.6.20 .......
> I saw it acquiring inode->i_mutex .
> Whats the need ?
> What are we safegaurding inode for.

See Documentation/filesystems/Locking and other files in that
directory for what i_mutex is supposed to protect.

XFS is different as it has it's own inodes and inode locks, but
it still mostly uses i_mutex inteh accepted way.

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
Need of inode->i_mutex in xfs_write(), kanishk rastogi Re: Need of inode->i_mutex in xfs_write(), David Chinner <=

Previous by Date:	XFS internal error XFS_WANT_CORRUPTED_RETURN, Markus Schoder
Next by Date:	Re: sb_ifree and sb_fdblocks are unequal, David Chinner
Previous by Thread:	Need of inode->i_mutex in xfs_write(), kanishk rastogi
Next by Thread:	sb_ifree and sb_fdblocks are unequal, Chris Pearson
Indexes:	[Date] [Thread] [Top] [All Lists]