On Tue, Feb 02, 2016 at 01:12:24PM +0100, Petr Mladek wrote: > > Hmm, the size of the offset is not a constant. In particular, leaf > functions do not set TOC before the mcount location. To be slightly more precise, a leaf function that additionally uses no global data. No global function calls, no global data access => no need to load the TOC. > For example, the code generated for int_to_scsilun() looks like: > > > 00000000000002d0 <int_to_scsilun>: > 2d0: a6 02 08 7c mflr r0 > 2d4: 10 00 01 f8 std r0,16(r1) > 2d8: 01 00 00 48 bl 2d8 <int_to_scsilun+0x8> > 2d8: R_PPC64_REL24 _mcount [...] > The above code is generated from kernel-4.5-rc1 sources using > > $> gcc --version > gcc (SUSE Linux) 4.8.5 > > But I get similar code also with > > $> gcc-6 --version > gcc-6 (SUSE Linux) 6.0.0 20160121 (experimental) [trunk revision 232670] > > > The result is that kernel crashes when trying to trace leaf function The trampoline *requires* a proper TOC pointer to find the remote function entry point. If you jump onto the trampoline with the TOC from the caller's caller you'll grab some address from somewhere and jump into nirvana. > By other words, it seems that the code generated with -mprofile-kernel > option has been buggy in all gcc versions. Either that or we need bigger trampolines for everybody. Michael, should we grow every module trampoline to always load R2, or fix GCC to recognise the generated bl _mcount as a global function call? Anton, what do you think? Torsten -- To unsubscribe from this list: send the line "unsubscribe live-patching" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
