On 9 Jun 2001, Trond Myklebust wrote:
> You forget to mention the main reason for the BKL in ->lookup():
> certain derived structures (struct inode springs to mind) get changed
> in various places in the code. Apart from the BKL there is no way yet
> to make those changes SMP-safe everywhere in the VFS.
That has nothing to ->lookup(). If it picks an existing inode - it has
no business changing it. If it creates a new one - there's nobody else
to touch it while we are filling the thing. _If_ you do filling the
inode after it's hashed and rely on BKL - that's a bug waiting to happen
that needs to be fixed.
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]
