On Wed, Dec 23, 2015 at 4:34 PM, Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx> wrote: > On Wed, Dec 23, 2015 at 04:11:22PM -0800, Tony Lindgren wrote: >> * Nicolas Pitre <nicolas.pitre@xxxxxxxxxx> [151223 13:45]: >> > We fixed a bunch of similar issues where code was located in the .data >> > section for ease of use from assembly code. See commit b4e61537 and >> > d0776aff for example. >> >> Thanks hey some assembly fun for the holidays :) I also need to check what >> all gets relocated to SRAM here. >> >> In any case, seems like the $subject patch is too intrusive for v4.5 at >> this point. > > Given Christmas and an unknown time between that and the merge window > actually opening, I decided Tuesday would be the last day I take any > patches into my tree - and today would be the day that I drop anything > that causes problems. > > So, I've already dropped this, so tomorrow's linux-next should not have > this change. > > You'll still see breakage if people enable RODATA though, but that's no > different from previous kernels. Ugh, sorry for the breakage. Should this patch stay as-is and people will fix their various RODATA failures during the next devel window, or should I remove the "default y if CPU_V7"? -Kees -- Kees Cook Chrome OS & Brillo Security -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>