Re: perf: use after free in perf_remove_from_context

[Peter Zijlstra]

On Wed, May 14, 2014 at 12:38:10PM -0400, Sasha Levin wrote:
> ./trinity -xinit_module -xreboot -xshutdown -xunshare -xnfsservctl -xclock_nanosleep -xuselib -xumount -xmount -m --quiet --dangerous -C 400 -l off
> 
> Note that I run it as root in a disposable VM. Running that as root on your
> machine will likely kill it.

Right, so i'll start with !root running. That said, I seem to get an
endless stream of double free or corrupt msgs:

trinity$ ./trinity -xinit_module -xreboot -xshutdown -xunshare -xnfsservctl -xclock_nanosleep -xuselib -xumount -xmount -m --quiet  -C 400 -l off

...

*** Error in `./trinity': double free or corruption (top): 0x000000000135af60 ***
[main] Random reseed: 3671679404
[main] Random reseed: 67838733
*** Error in `./trinity': double free or corruption (top): 0x000000000135ef60 ***
[main] Random reseed: 943044433
*** Error in `./trinity': double free or corruption (top): 0x00000000012bb210 ***
[main] Random reseed: 3627649145
*** Error in `./trinity': double free or corruption (top): 0x000000000139dbe0 ***
[main] Random reseed: 935036390
[main] Random reseed: 3922349807
[main] Random reseed: 835563887
*** Error in `./trinity': double free or corruption (top): 0x0000000001323890 ***
[main] Random reseed: 974945617
*** Error in `./trinity': double free or corruption (top): 0x0000000001308190 ***
[main] Random reseed: 2912296953
[main] Random reseed: 681900861


Is this 'expected' behaviour?

trinity$ git describe
1.1-1418-g8bf4840

Attachment: pgpIHkpQ7YrWw.pgp
Description: PGP signature