Searched hist:"3 cfc096e4c4fbc234634cf8a30d40348a25fc9ba" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/arch/xtensa/kernel/ |
| H A D | vectors.S | diff 3cfc096e4c4fbc234634cf8a30d40348a25fc9ba Wed Aug 06 16:03:01 CDT 2014 Max Filippov <jcmvbkbc@gmail.com> xtensa: don't allow overflow/underflow on unaligned stack
Double exceptions that happen during register window overflow/underflow
are handled in the topmost stack frame, as if it was the only exception
that occured. However unaligned access exception handler is special
because it needs to analyze instruction that caused the exception, but
the userspace instruction that triggered window exception is completely
irrelevant. Unaligned data access is rather normal in the generic
userspace code, but stack pointer manipulation must always be done by
architecture-aware code and thus unaligned stack means a serious problem
anyway.
Use the default unaligned access handler that raises SIGBUS in case
of unaligned access in window overflow/underflow handler.
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
|
| H A D | vmlinux.lds.S | diff 3cfc096e4c4fbc234634cf8a30d40348a25fc9ba Wed Aug 06 16:03:01 CDT 2014 Max Filippov <jcmvbkbc@gmail.com> xtensa: don't allow overflow/underflow on unaligned stack
Double exceptions that happen during register window overflow/underflow
are handled in the topmost stack frame, as if it was the only exception
that occured. However unaligned access exception handler is special
because it needs to analyze instruction that caused the exception, but
the userspace instruction that triggered window exception is completely
irrelevant. Unaligned data access is rather normal in the generic
userspace code, but stack pointer manipulation must always be done by
architecture-aware code and thus unaligned stack means a serious problem
anyway.
Use the default unaligned access handler that raises SIGBUS in case
of unaligned access in window overflow/underflow handler.
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
|
| H A D | traps.c | diff 3cfc096e4c4fbc234634cf8a30d40348a25fc9ba Wed Aug 06 16:03:01 CDT 2014 Max Filippov <jcmvbkbc@gmail.com> xtensa: don't allow overflow/underflow on unaligned stack
Double exceptions that happen during register window overflow/underflow
are handled in the topmost stack frame, as if it was the only exception
that occured. However unaligned access exception handler is special
because it needs to analyze instruction that caused the exception, but
the userspace instruction that triggered window exception is completely
irrelevant. Unaligned data access is rather normal in the generic
userspace code, but stack pointer manipulation must always be done by
architecture-aware code and thus unaligned stack means a serious problem
anyway.
Use the default unaligned access handler that raises SIGBUS in case
of unaligned access in window overflow/underflow handler.
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
|