From: "Liam R. Howlett" <Liam.Howlett@xxxxxxxxxx> Date: Tue, 17 Jan 2017 10:59:01 -0500 > A non-resumable error from userspace is able to cause a kernel panic or trap > loop due to the setup and handling of the queued traps once in the kernel. > This patch series addresses both of these issues. > > The queues are fixed by simply zeroing the memory before use. > > PIO errors from userspace will result in a SIGBUS being sent to the user > process. > > The MEM errors form userspace will result in a SIGKILL and also cause the > offending pages to be claimed so they are no longer used in future tasks. > SIGKILL is used to ensure that the process does not try to coredump and result > in an attempt to read the memory again from within kernel space. Although > there is a HV call to scrub the memory (mem_scrub), there is no easy way to > guarantee that the real memory address(es) are not used by other tasks. > Clearing the error with mem_scrub would zero the memory and cause the other > processes to proceed with bad data. > > The handling of other non-resumable errors remain unchanged and will cause a > panic. > > > Changelog v2 to v3: > Fix newline in an expression as an argument. > Remove extra new line. Looks good, series applied, thanks Liam! -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
