From: Mikulas Patocka <mpatocka@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Vegard Nossum <vegard.nossum@oracle.com>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Frank Scheiner <frank.scheiner@web.de>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
Helge Deller <deller@gmx.de>,
John David Anglin <dave@parisc-linux.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-parisc@vger.kernel.org, linux-mm@kvack.org
Subject: [PATCH] parisc: fix inability to allocate stack pages on exec
Date: Mon, 3 Jul 2023 21:58:41 +0200 (CEST) [thread overview]
Message-ID: <ccadf5d7-e22a-ab5b-21e8-18a788251845@redhat.com> (raw)
Hi
The patch 8d7071af8907 ("mm: always expand the stack with the mmap write
lock held") breaks PA-RISC.
The breakage happens if we attempt to pass more arguments to execve than
what fits into the initial stack page - we get -E2BIG in such a case.
The reason for the breakage is that the commit 8d7071af8907 adds the test
"if (!(vma->vm_flags & VM_GROWSDOWN)) return -EFAULT;" to the function
expand_downwards.
expand_downwards is called from get_arg_page to allocate initial stack
pages. With the added test for VM_GROWSDOWN, it is not able to allocate
any pages on PA-RISC at all, and execve fails as soon as it tries to
allocate a stack page.
The bug can be fixed by dropping the test for VM_GROWSDOWN from
expand_downwards.
Fixes: 8d7071af8907 ("mm: always expand the stack with the mmap write lock held")
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Cc: stable@vger.kernel.org # v6.4
---
mm/mmap.c | 3 ---
1 file changed, 3 deletions(-)
Index: linux-6.4.1/mm/mmap.c
===================================================================
--- linux-6.4.1.orig/mm/mmap.c 2023-07-03 18:17:35.000000000 +0200
+++ linux-6.4.1/mm/mmap.c 2023-07-03 21:22:44.000000000 +0200
@@ -2036,9 +2036,6 @@ int expand_downwards(struct vm_area_stru
struct vm_area_struct *prev;
int error = 0;
- if (!(vma->vm_flags & VM_GROWSDOWN))
- return -EFAULT;
-
address &= PAGE_MASK;
if (address < mmap_min_addr || address < FIRST_USER_ADDRESS)
return -EPERM;
next reply other threads:[~2023-07-03 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 19:58 Mikulas Patocka [this message]
2023-07-03 20:06 ` Linus Torvalds
2023-07-03 20:40 ` Mikulas Patocka
2023-07-03 20:42 ` Linus Torvalds
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=ccadf5d7-e22a-ab5b-21e8-18a788251845@redhat.com \
--to=mpatocka@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=dave@parisc-linux.org \
--cc=deller@gmx.de \
--cc=frank.scheiner@web.de \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-mm@kvack.org \
--cc=linux-parisc@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vegard.nossum@oracle.com \
/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