On Mon, 5 Mar 2018, Michael Schmitz wrote:
About evading a signal - as the code is now, any faults that are not write protect or invalid MMU descriptor faults would end up in that branch. In particular, for anything that should have been caught by the branch below, we'd expect to see kernel mode faults cause signals or unexpected bus errors that should really have caused a panic. I've never seen these unexpected bus errors in my logs.
What raises that signal in the !(mmusr & (MMU_I | MMU_WP)) && (ssw & RM) case? -- -- To unsubscribe from this list: send the line "unsubscribe linux-m68k" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
