Re: Odd SIGSEGV issue introduced by commit 6b31d5955cb29 ("mm, oom: fix potential data corruption when oom_reaper races with writer")
From: Michael Ellerman <mpe@ellerman.id.au>
Date: 2018-08-23 01:26:03
Also in:
linux-mm
Christophe LEROY [off-list ref] writes:
Hello, I have an odd issue on my powerpc 8xx board. I am running latest 4.14 and get the following SIGSEGV which appears more or less randomly. [ 9.190354] touch[91]: unhandled signal 11 at 67807b58 nip 777cf114 lr 777cf100 code 30001 [ 24.634810] ifconfig[160]: unhandled signal 11 at 67ae7b58 nip 77aaf114 lr 77aaf100 code 30001
It would be interesting to see the code dump here and which registers are being used. Can you backport the show unhandled signal changes and see what that shows us? cheers