On Mon, Aug 18, 2008 at 12:52:08AM +0200, Sven Wegener wrote: > We can't access the cache entry outside of our critical read-locked region, > because someone may free that entry. And we also need to check in the critical > region wether the destination is still available, i.e. it's not in the trash. > If we drop our reference counter, the destination can be purged from the trash > at any time. Our caller only guarantees that no destination is moved to the > trash, while we are scheduling. Also there is no need for our own rwlock, > there is already one in the service structure for use in the schedulers. Hi Sven, I need to look over these changes with a fresh set of eyes in the morning - sorry that I didn't do that earlier today. I am very much in favour of the changes that we made last week, and this patch at least looks a lot like the changes we discussed. Do you think these should be pushed into 2.6.27? Or perhaps even stable? They are real races, right? -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
