From: James Morris <jmorris@namei.org>
To: Eric Paris <eparis@redhat.com>
Cc: linux-kernel@vger.kernel.org, Stephen Smalley <sds@tycho.nsa.gov>,
selinux@tycho.nsa.gov, alan@redhat.com, chrisw@redhat.com,
hpa@zytor.com, Andrew Morton <akpm@linux-foundation.org>,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH 1/3] mmap: protect from stack expantion into low vm addresses
Date: Tue, 27 Nov 2007 12:04:18 +1100 (EST) [thread overview]
Message-ID: <Xine.LNX.4.64.0711271201240.17892@us.intercode.com.au> (raw)
In-Reply-To: <1196120846.16779.12.camel@localhost.localdomain>
On Mon, 26 Nov 2007, Eric Paris wrote:
> Add security checks to make sure we are not attempting to expand the
> stack into memory protected by mmap_min_addr
>
> Signed-off-by: Eric Paris <eparis@redhat.com>
Please include the LSMs list in the CC line (added again) for posts
relating to security.
Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/selinux-2.6.git#for-akpm
> ---
>
> ** Be very careful applying/rediffing this patch. Standard 3 lines of
> context from git diff will misapply the first hunk to expand_upwards
> instead of properly in expand_downwards. This patch was generated using
> -U 4 to make sure it applies in the correct place. **
Seems to have applied correctly for me.
>
> mm/mmap.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> --- kernel-1/mm/mmap.c
> +++ kernel-2/mm/mmap.c
> @@ -1614,17 +1614,21 @@ static inline int expand_downwards(struc
> * so that the anon_vma locking is not a noop.
> */
> if (unlikely(anon_vma_prepare(vma)))
> return -ENOMEM;
> +
> + address &= PAGE_MASK;
> + error = security_file_mmap(0, 0, 0, 0, address, 1);
> + if (error)
> + return error;
> +
> anon_vma_lock(vma);
>
> /*
> * vma->vm_start/vm_end cannot change under us because the caller
> * is required to hold the mmap_sem in read mode. We need the
> * anon_vma lock to serialize against concurrent expand_stacks.
> */
> - address &= PAGE_MASK;
> - error = 0;
>
> /* Somebody else might have raced and expanded it already */
> if (address < vma->vm_start) {
> unsigned long size, grow;
>
>
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2007-11-27 1:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 23:47 [PATCH 1/3] mmap: protect from stack expantion into low vm addresses Eric Paris
2007-11-27 1:04 ` James Morris [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-16 20:54 Eric Paris
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=Xine.LNX.4.64.0711271201240.17892@us.intercode.com.au \
--to=jmorris@namei.org \
--cc=akpm@linux-foundation.org \
--cc=alan@redhat.com \
--cc=chrisw@redhat.com \
--cc=eparis@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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