On Tue, Jan 27, 2015 at 1:12 PM, Jan Engelhardt <jengelh@xxxxxxx> wrote:
>
> The 2nd patch (from 12:57:20 -0800) plus the one-liner for mm/memory.c
> at the callsite for check_stack_guard_page makes the test still
> not succeed.
Really? What platform? I get
==================
All 5 tests passed
==================
with the patch I sent out, combined with this:
diff --git a/mm/memory.c b/mm/memory.c
index 54f3a9b00956..2c3536cc6c63 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -2632,7 +2632,7 @@ static int do_anonymous_page(struct mm_struct
*mm, struct vm_area_struct *vma,
/* Check if we need to add a guard page to the stack */
if (check_stack_guard_page(vma, address) < 0)
- return VM_FAULT_SIGBUS;
+ return VM_FAULT_SIGSEGV;
/* Use the zero-page for reads */
if (!(flags & FAULT_FLAG_WRITE) && !mm_forbids_zeropage(mm)) {
but since architecture matters, and I run on x86-64, some other
platform might still have issues.
(And yes, I checked that it failed without the patch, so I think I'm
testing the same thing you guys are)
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-arch" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
