On Tue, 29 Feb 2000, William Montgomery wrote:
>Could you explain again what the problem is when we always allow
>schedule?
As soon as you drop the inode_lock spinlock the variable called "entry"
gets invalidated and you have to revalidate it as soon as you reacquire
the lock or you risk to reference something that is not there anymore.
(Side note: In practice the inode.c in 2.2.x is called always with the big
kernel lock held so in practice it's only the schedule() that invalidates
the variable called "entry" but don't relay on this! ;)
Andrea
-
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/
This archive was generated by hypermail 2b29 : Tue Feb 29 2000 - 21:00:22 EST