Re: [PATCH 3.4 007/125] recordmcount: Fix endianness handling bug for nop_mcount

2016-10-12 Thread Zefan Li
On 2016/10/12 21:10, Steven Rostedt wrote: > Hi Li, > > What is your plan for EOL of 3.4? I see on kernel.org that the EOL of > 3.4 was suppose to be September 2016 (which has passed). I just gave a > talk yesterday saying it is no longer supported. But I appear to be > mistaken. > I think I'll

Re: [PATCH 3.4 007/125] recordmcount: Fix endianness handling bug for nop_mcount

2016-10-12 Thread Steven Rostedt
Hi Li, What is your plan for EOL of 3.4? I see on kernel.org that the EOL of 3.4 was suppose to be September 2016 (which has passed). I just gave a talk yesterday saying it is no longer supported. But I appear to be mistaken. https://www.kernel.org/category/releases.html -- Steve

[PATCH 3.4 007/125] recordmcount: Fix endianness handling bug for nop_mcount

2016-10-12 Thread lizf
From: libin 3.4.113-rc1 review patch. If anyone has any objections, please let me know. -- commit c84da8b9ad3761eef43811181c7e896e9834b26b upstream. In nop_mcount, shdr->sh_offset and welp->r_offset should handle endianness properly, otherwise it will trigger Segmentation fau