https://bugzilla.kernel.org/show_bug.cgi?id=212955 --- Comment #11 from Lucas Endres (jaffa225man@xxxxxxxxx) --- (In reply to Lucas Endres from comment #10) > In the next few days I hope to have time to attempt bisection to get to the > bottom of it all. Sorry it took me so long (please let me know if it's been noticed and fixed already), but I finally have gotten through all the bisects to reveal this commit (I don't think it's what anyone was expecting): 51e6f07cb12e50bfc71181bd08bad5f0a9b5e9e2 is the first bad commit commit 51e6f07cb12e50bfc71181bd08bad5f0a9b5e9e2 Merge: 5e321ded30 6b3788e5fb Author: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> Date: Tue May 4 10:48:05 2021 -0700 Merge tag 'm68knommu-for-v5.13' of git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu Pull m68knommu updates from Greg Ungerer: - a fix for interrupt number range checking for the ColdFire SIMR interrupt controller. - changes for the binfmt_flat binary loader to allow RISC-V nommu support it needs to be able to accept flat binaries that have no gap between the text and data sections. * tag 'm68knommu-for-v5.13' of git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu: m68k: coldfire: fix irq ranges riscv: Disable data start offset in flat binaries binfmt_flat: allow not offsetting data start arch/m68k/coldfire/intc-simr.c | 12 ++++++------ arch/riscv/Kconfig | 1 + fs/Kconfig.binfmt | 3 +++ fs/binfmt_flat.c | 18 +++++++++++++----- 4 files changed, 23 insertions(+), 11 deletions(-) Thanks for any suggestions I may be needing to test, Lucas -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
