| To: | xfs-masters@xxxxxxxxxxx |
|---|---|
| Subject: | [xfs-masters] [Bug 7632] Race: a lock should be acquired before calling bhv_base_unlocked |
| From: | bugme-daemon@xxxxxxxxxxxxxxxxxxx |
| Date: | Wed, 6 Dec 2006 14:36:31 -0800 |
| Reply-to: | xfs-masters@xxxxxxxxxxx |
| Sender: | xfs-masters-bounce@xxxxxxxxxxx |
http://bugzilla.kernel.org/show_bug.cgi?id=7632 ------- Additional Comments From cattelan@xxxxxxx 2006-12-06 14:33 ------- That comment is a left over from the original version of bhv_base_unlocked. The function originally would lock the behavior chain when doing the lookup here, the the unlocked portion of the name. The unlocked in the function name was to signify the caller has not taken a read lock on the behavior chain and therefore the function is required to take the lock. One the linux the behavior chains are static once they are set up at mount time and not dynamically changing, therefore the locks were dropped from the linux implementation of behaviors. That comment should probably be removed as it is mis-leading. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [xfs-masters] [Bug 3224] XFS internal error xfs_iformat(6) at line 546 of file fs/xfs/xfs_inode.c, bugme-daemon |
|---|---|
| Next by Date: | [xfs-masters] [Bug 3224] XFS internal error xfs_iformat(6) at line 546 of file fs/xfs/xfs_inode.c, bugme-daemon |
| Previous by Thread: | [xfs-masters] [Bug 7632] Race: a lock should be acquired before calling bhv_base_unlocked, bugme-daemon |
| Next by Thread: | [xfs-masters] [Bug 7632] Race: a lock should be acquired before calling bhv_base_unlocked, bugme-daemon |
| Indexes: | [Date] [Thread] [Top] [All Lists] |