2016-06-23 15:40 GMT+03:00 Dmitry Vyukov <dvyukov@xxxxxxxxxx>: > On Thu, Jun 23, 2016 at 1:50 PM, Andrey Ryabinin <ryabinin.a.a@xxxxxxxxx> wrote: >> 2016-06-23 14:49 GMT+03:00 Andrey Ryabinin <ryabinin.a.a@xxxxxxxxx>: >> >>> Frankly, I don't understand why .text.[exit,startup] sections has any relation >>> to the bug you described, but maybe I just don't now linker >> >> ... scripting well enough to understand what's going on here. > > > I noticed that these 3 new sections are what's different between > kernel that works and kernel that does not work. So I decided to > account all of them > Checked now, it works only with .dtors. > Is it preferable to add only .dtors or all sections? No. Merging text.startup/text.exit into INIT_TEXT/EXIT_TEXT makes sense anyway. This will save us some memory. Also we can add .fini_array into DISCARD section, because we don't need destructors. As for .dtors, at first I'd like to understand where it comes from. AFAIU it shouldn't exist at all. Recent gcc should generate .fini_array instead of .dtors - https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46770 So something is wrong here. Can you share your kernel .config, kernel version? And you use gcc-6.1.0, right? -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
