On Wednesday, September 26, 2018 4:18:19 PM CEST Arnaldo Carvalho de Melo wrote: > Em Wed, Sep 26, 2018 at 03:52:05PM +0200, Milian Wolff escreveu: > > Fixes a crash when the report encounters an address that > > > could not be associated with an mmaped region: > Milian, can you spot which cset introduced this problem? So that we can > add a "Fixes: sha" tag in this (and the others, if needed) to help the > stable kernel maintainers to find which kernels this has to be > backported to?
The issue was introduced by perf script: Show correct offsets for DWARF-based unwinding This in turn got backported already a few times, at which point the 2a9d5050dc84fa2060f08a52f632976923e0fa7e sha was used when referencing the "Upstream commit". Is that enough, or do you need me to find all the backported shas too? -- Milian Wolff | milian.wo...@kdab.com | Senior Software Engineer KDAB (Deutschland) GmbH, a KDAB Group company Tel: +49-30-521325470 KDAB - The Qt, C++ and OpenGL Experts
smime.p7s
Description: S/MIME cryptographic signature