On Wed, Jun 10, 2015 at 03:32:24PM -0700, Jarno Rajahalme wrote: > Postponed 'next' member poisoning was based on the faulty assumption > that postponed functions would be called in the order they were > postponed. This assumption holds only for the functions postponed by > any single thread. When functions are postponed by different > threads, there are no guarantees of the order in which the functions > may be called, or timing between those calls after the next grace > period has passed. > > Given this, the postponed poisoning could have executed after > postponed destruction of the object containing the rculist element. > > This bug was revealed after the memory leaks on rule deletion were > recently fixed. > > This patch removes the postponed 'next' member poisoning and adds > documentation describing the ordering limitations in OVS RCU. > > Alex Wang dug out the root cause of the resulting crashes, thanks! > > Signed-off-by: Jarno Rajahalme <jrajaha...@nicira.com>
I get patch rejects against current master, can you rebase? Thanks, Ben. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
