From: Oleg Nesterov <oleg@redhat.com>
To: Denys Vlasenko <dvlasenk@redhat.com>
Cc: linuxppc-dev@lists.ozlabs.org,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Kees Cook <keescook@chromium.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Florian Weimer <fweimer@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] powerpc: Do not make the entire heap executable
Date: Wed, 10 Aug 2016 15:36:21 +0200 [thread overview]
Message-ID: <20160810133621.GA30167@redhat.com> (raw)
In-Reply-To: <20160810130030.5268-1-dvlasenk@redhat.com>
On 08/10, Denys Vlasenko wrote:
>
> Currently, to support 32-bit binaries with PLT in BSS kernel maps *entire
> brk area* with executable rights for all binaries, even --secure-plt ones.
>
> Stop doing that.
Can't really review this patch, but at least the change in mm/mmap.c looks
technically correct to me... One nit below, feel free to ignore.
> @@ -2668,7 +2668,7 @@ static int do_brk(unsigned long addr, unsigned long request)
> if (!len)
> return 0;
>
> - flags = VM_DATA_DEFAULT_FLAGS | VM_ACCOUNT | mm->def_flags;
> + flags |= VM_DATA_DEFAULT_FLAGS | VM_ACCOUNT | mm->def_flags;
OK. But note that we have
mlock_future_check(mm->def_flags);
a few lines below and after this change this _looks_ wrong because
VM_LOCKED can come from the new "flags" argument passed to do_brk().
Nobody does this right now, still this looks wrong/confusing.
I'd suggest to add another change
- mlock_future_check(mm->def_flags);
+ mlock_future_check(flags);
or add a sanity check at the start to deny VM_LOCKED and perhaps
something else...
The same for vm_brk_flags() which after your change does
do_brk_flags(flags);
populate = (mm->def_flags & VM_LOCKED);
again, this is just a nit, I do not think it will be ever called
with VM_LOCKED in "flags".
Oleg.
next prev parent reply other threads:[~2016-08-10 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 13:00 [PATCH v4] powerpc: Do not make the entire heap executable Denys Vlasenko
2016-08-10 13:36 ` Oleg Nesterov [this message]
2016-08-19 12:33 ` Denys Vlasenko
2016-08-21 15:47 ` Aneesh Kumar K.V
2016-08-22 18:37 ` Denys Vlasenko
2016-08-22 19:22 ` Jason Gunthorpe
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=20160810133621.GA30167@redhat.com \
--to=oleg@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=dvlasenk@redhat.com \
--cc=fweimer@redhat.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
/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).