From: Daniel Axtens <dja@axtens.net>
To: linuxppc-dev@lists.ozlabs.org
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Daniel Black <daniel@linux.ibm.com>,
Daniel Axtens <dja@axtens.net>
Subject: [PATCH] powerpc/fault: kernel can extend a user process's stack
Date: Wed, 11 Dec 2019 12:43:37 +1100 [thread overview]
Message-ID: <20191211014337.28128-1-dja@axtens.net> (raw)
If a process page-faults trying to write beyond the end of its
stack, we attempt to grow the stack.
However, if the kernel attempts to write beyond the end of a
process's stack, it takes a bad fault. This can occur when the
kernel is trying to set up a signal frame.
Permit the kernel to grow a process's stack. The same general
limits as to how and when the stack can be grown apply: the kernel
code still passes through expand_stack(), so anything that goes
beyond e.g. the rlimit should still be blocked.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=205183
Reported-by: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Daniel Black <daniel@linux.ibm.com>
Signed-off-by: Daniel Axtens <dja@axtens.net>
---
arch/powerpc/mm/fault.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/arch/powerpc/mm/fault.c b/arch/powerpc/mm/fault.c
index b5047f9b5dec..00183731ea22 100644
--- a/arch/powerpc/mm/fault.c
+++ b/arch/powerpc/mm/fault.c
@@ -287,7 +287,17 @@ static bool bad_stack_expansion(struct pt_regs *regs, unsigned long address,
if (!res)
return !store_updates_sp(inst);
*must_retry = true;
+ } else if ((flags & FAULT_FLAG_WRITE) &&
+ !(flags & FAULT_FLAG_USER)) {
+ /*
+ * the kernel can also attempt to write beyond the end
+ * of a process's stack - for example setting up a
+ * signal frame. We assume this is valid, subject to
+ * the checks in expand_stack() later.
+ */
+ return false;
}
+
return true;
}
return false;
--
2.20.1
next reply other threads:[~2019-12-11 1:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 1:43 Daniel Axtens [this message]
2019-12-11 6:14 ` [PATCH] powerpc/fault: kernel can extend a user process's stack Daniel Black
2019-12-11 7:28 ` Michal Suchánek
2019-12-11 9:37 ` Daniel Axtens
2020-07-20 10:51 ` Michal Suchánek
2020-07-20 13:52 ` Michael Ellerman
2020-07-21 0:57 ` Daniel Axtens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191211014337.28128-1-dja@axtens.net \
--to=dja@axtens.net \
--cc=daniel@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tgl@sss.pgh.pa.us \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).