On Tue, 2011-05-03 at 16:55 +1000, Anton Blanchard wrote: > Hi Ben, > > > My only comment (sorry Anton :-) would have been that we could lazily > > allocate the spinlock on the first use_cop() ... or do we have that > > potentially called in the wrong context ? > > I worry what might happen in a threaded app. It would be a strange > thing to do, but the program may call use_cop from two threads at the > same time. In that case you could corrupt the PID/ACOP values > and leak a spinlock of memory I think.
OK, it's a bit nasty to solve. I'll put the latest patch in my queue and if all goes well, it should hit next by the end of the week. Cheers, Ben. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
