Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1458712

Re: perf: WARNING: kernel/events/core.c:4893 perf_mmap_close

Show all headers | View raw

and as the fuzzing continues I started to get these, a bit worrying.

[ 6501.254564] Slab corruption (Tainted: G        W      ): task_struct start=ffff8800c072e000, len=5760
[ 6501.264971] 010: 6a 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b  jkkkkkkkkkkkkkkk
[ 6501.273650] Single bit error detected. Probably bad RAM.
[ 6501.279889] Run memtest86+ or a similar memory test tool.

[19535.776930] Slab corruption (Tainted: G        W      ): task_struct start=ffff8800c720e2c0, len=5760
[19535.787191] 010: 6a 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b  jkkkkkkkkkkkkkkk
[19535.795771] Single bit error detected. Probably bad RAM.
[19535.801872] Run memtest86+ or a similar memory test tool.

Is it possible this was a decrement-after-free bug?

It could also be bad RAM I suppose, I was using this machine to do some 
pretty intense DRAM RAPL validation which involved a lot of DIMM swapping 
so it is conceivable that I managed to break something.

Also lots of
[ 4714.797333] perfevents: irq loop stuck!
errors as always, I think we decided those were probably a hardware issue.

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

perf: WARNING: kernel/events/core.c:4893 perf_mmap_close Vince Weaver <vincent.weaver@maine.edu> - 2016-08-08 22:30 +0200
  Re: perf: WARNING: kernel/events/core.c:4893 perf_mmap_close Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2016-08-09 07:20 +0200
    Re: perf: WARNING: kernel/events/core.c:4893 perf_mmap_close Vince Weaver <vincent.weaver@maine.edu> - 2016-08-09 14:50 +0200
    Re: perf: WARNING: kernel/events/core.c:4893 perf_mmap_close Vince Weaver <vincent.weaver@maine.edu> - 2016-08-09 15:00 +0200

csiph-web