On Wed, Apr 23, 2008 at 11:09:35AM -0700, Christoph Lameter wrote: > Why is there still the hlist stuff being used for the mmu notifier list? > And why is this still unsafe?
What's the problem with hlist, it saves 8 bytes for each mm_struct, you should be using it too instead of list. > There are cases in which you do not take the reverse map locks or mmap_sem > while traversing the notifier list? There aren't. > This hope for inclusion without proper review (first for .25 now for .26) > seems to interfere with the patch cleanup work and cause delay after delay > for getting the patch ready. On what basis do you think that there is a > chance of any of these patches making it into 2.6.26 given that this > patchset has never been vetted in Andrew's tree? Let's say I try to be optimistic and hope the right thing will happen given this is like a new driver that can't hurt anybody but KVM and GRU if there's any bug. But in my view what interfere with proper review for .26 are the endless discussions we're doing ;). ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
