From: Oleg Nesterov <oleg@redhat.com>
To: Kees Cook <keescook@chromium.org>
Cc: Rik van Riel <riel@redhat.com>, Michal Hocko <mhocko@suse.com>,
Stanislav Kozina <skozina@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: get_arg_page() && ptr_size accounting
Date: Mon, 10 Sep 2018 19:21:09 +0200 [thread overview]
Message-ID: <20180910172109.GB27005@redhat.com> (raw)
In-Reply-To: <CAGXu5jJ+aiJWL0G0Zpq2Df4ADEmpSBZHSTaUkzJiNbgg+B6x2Q@mail.gmail.com>
On 09/10, Kees Cook wrote:
>
> On Mon, Sep 10, 2018 at 9:41 AM, Kees Cook <keescook@chromium.org> wrote:
> > On Mon, Sep 10, 2018 at 5:29 AM, Oleg Nesterov <oleg@redhat.com> wrote:
> >> Hi Kees,
> >>
> >> I was thinking about backporting the commit 98da7d08850fb8bde
> >> ("fs/exec.c: account for argv/envp pointers"), but I am not sure
> >> I understand it...
>
> BTW, if you backport that, please get the rest associated with the
> various Stack Clash related weaknesses:
may be...
> da029c11e6b1 exec: Limit arg stack to at most 75% of _STK_LIM
and I have to admit that I do not understand this patch at all, the
changelog explains nothing.
Could you explain what this patch actually prevents from? Especially
now that we have stack_guard_gap?
Oleg.
next prev parent reply other threads:[~2018-09-10 17:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 12:29 get_arg_page() && ptr_size accounting Oleg Nesterov
2018-09-10 16:41 ` Kees Cook
2018-09-10 16:45 ` Kees Cook
2018-09-10 17:21 ` Oleg Nesterov [this message]
2018-09-10 17:43 ` Oleg Nesterov
2018-09-11 4:30 ` Kees Cook
2018-09-11 15:29 ` Oleg Nesterov
2018-09-11 4:27 ` Kees Cook
2018-09-11 15:25 ` Oleg Nesterov
2018-09-10 17:18 ` Oleg Nesterov
2018-09-11 4:23 ` Kees Cook
2018-09-11 14:13 ` Oleg Nesterov
2018-09-11 19:06 ` Kees Cook
2018-09-12 12:27 ` Oleg Nesterov
2018-09-12 14:23 ` Oleg Nesterov
2018-09-12 20:42 ` Kees Cook
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=20180910172109.GB27005@redhat.com \
--to=oleg@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=riel@redhat.com \
--cc=skozina@redhat.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;
as well as URLs for NNTP newsgroup(s).