mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-24 21:24:00 +08:00
33692f2759
The core VM already knows about VM_FAULT_SIGBUS, but cannot return a
"you should SIGSEGV" error, because the SIGSEGV case was generally
handled by the caller - usually the architecture fault handler.
That results in lots of duplication - all the architecture fault
handlers end up doing very similar "look up vma, check permissions, do
retries etc" - but it generally works. However, there are cases where
the VM actually wants to SIGSEGV, and applications _expect_ SIGSEGV.
In particular, when accessing the stack guard page, libsigsegv expects a
SIGSEGV. And it usually got one, because the stack growth is handled by
that duplicated architecture fault handler.
However, when the generic VM layer started propagating the error return
from the stack expansion in commit
|
||
|---|---|---|
| .. | ||
| cache-dbg-flush-by-reg.S | ||
| cache-dbg-flush-by-tag.S | ||
| cache-dbg-inv-by-reg.S | ||
| cache-dbg-inv-by-tag.S | ||
| cache-dbg-inv.S | ||
| cache-disabled.c | ||
| cache-flush-by-reg.S | ||
| cache-flush-by-tag.S | ||
| cache-flush-icache.c | ||
| cache-inv-by-reg.S | ||
| cache-inv-by-tag.S | ||
| cache-inv-icache.c | ||
| cache-smp-flush.c | ||
| cache-smp-inv.c | ||
| cache-smp.c | ||
| cache-smp.h | ||
| cache.c | ||
| cache.inc | ||
| dma-alloc.c | ||
| extable.c | ||
| fault.c | ||
| init.c | ||
| Kconfig.cache | ||
| Makefile | ||
| misalignment.c | ||
| mmu-context.c | ||
| pgtable.c | ||
| tlb-mn10300.S | ||
| tlb-smp.c | ||