Re: lock/unlock_super and inode bitmaps.

Tigran Aivazian (tigran@sco.COM)
Wed, 27 Oct 1999 08:06:10 +0100 (BST)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Marc Lefranc: "[2.2.13] Oops after sys_newlstat"
Previous message: Tigran Aivazian: "lock/unlock_super and inode bitmaps."

On Wed, 27 Oct 1999, Tigran Aivazian wrote:
> The only lock taken at the VFS level is lock_parent() so two things with
> different parents can still corrupt super_block info.

Ironically, in my specific case (BFS) there is only one directory so
taking lock_parent() at VFS level is sufficient but I certainly would like
to know the correct answer in generic case anyway.

Thanks,
Tigran.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

Next message: Marc Lefranc: "[2.2.13] Oops after sys_newlstat"
Previous message: Tigran Aivazian: "lock/unlock_super and inode bitmaps."