From: Laura Abbott <labbott@redhat.com>
To: "Kees Cook" <keescook@chromium.org>, "Tomáš Trnka" <trnka@scm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Stephen Smalley <sds@tycho.nsa.gov>,
Paul Moore <pmoore@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: System-wide hard RLIMIT_STACK in 4.14.4+ w/ SELinux
Date: Tue, 12 Dec 2017 11:52:57 -0800 [thread overview]
Message-ID: <b32848cf-a6e2-c918-e697-2066799a31fc@redhat.com> (raw)
In-Reply-To: <CAGXu5j+e1kd7gHk9qVUhy6Ubc6c3PBm_zTM9kqkd+UkD9qr6KQ@mail.gmail.com>
On 12/12/2017 11:23 AM, Kees Cook wrote:
> On Tue, Dec 12, 2017 at 2:58 AM, Tomáš Trnka <trnka@scm.com> wrote:
>> Hello,
>>
>> Commit 04e35f4495dd560db30c25efca4eecae8ec8c375 "exec: avoid RLIMIT_STACK
>> races with prlimit()" that made it into 4.14.4 effectively changes the default
>> hard RLIMIT_STACK on machines with SELinux (seen on Fedora 27).
>>
>> selinux_bprm_set_creds() sets bprm->secureexec for any SELinux domain
>> transition that does not have the "noatsecure" permission. The secureexec
>> logic thus kicks in for virtually every process launched by PID 1 systemd
>> (init_t), including gettys, display managers, etc.
>
> Uuugh. Okay, we need to revert that commit. I'll send a patch for 4.15
> (with a fix for -stable too).
>
> I will design an alternative, which was considered much earlier:
> keeping a copy of the rlimits in the bprm during exec so it can't
> change out from under the execing process. This will avoid needing to
> set the hard limit, avoid the locking race that commit was trying to
> fix, etc.
>
> This is an interesting state for the system to be in, though, it means
> AT_SECURE is being set for virtually all processes too? I would expect
> that might break a lot too (but clearly it hasn't).
>
>>
>> I can see that 8 MiB "should be enough for everyone" using normal software,
>> but sadly the HPC stuff around here tends to need a little more (due to a
>> deficiency in gfortran).
>>
>> Minimal example (the actual types are not too important):
>>
>> # /bin/ulimit -Hs
>> unlimited
>> # runcon -r system_r -t sysadm_t runcon -t rpm_script_t /bin/ulimit -Hs
>> 8192
>>
>> Of course this can be somewhat worked around by adjusting the SELinux policy
>> (allowing blanket noatsecure permission for init_t and possibly others) or by
>> pam_limits (for components using PAM). Unfortunately, systemd's LimitSTACK= is
>> also broken (calls setrlimit before exec). Anyway, I wasn't expecting any of
>> that in connection with the 4.14.3->.4 upgrade.
>>
>> --
>> Best regards,
>>
>> Tomáš Trnka
>> Software for Chemistry & Materials
>
> Thanks for the report and examples!
>
> -Kees
>
FWIW, the issue I reported offline yesterday
https://bugzilla.redhat.com/show_bug.cgi?id=1524083 still happens with
selinux disabled. The conclusion there is still that trafficserver
needs to be fixed.
Thanks,
Laura
next prev parent reply other threads:[~2017-12-12 19:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 10:58 System-wide hard RLIMIT_STACK in 4.14.4+ w/ SELinux Tomáš Trnka
2017-12-12 15:44 ` Tomáš Trnka
2017-12-12 19:23 ` Kees Cook
2017-12-12 19:36 ` Tomáš Trnka
2017-12-12 19:52 ` Laura Abbott [this message]
2017-12-12 19:56 ` Kees Cook
2017-12-12 20:10 ` Laura Abbott
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=b32848cf-a6e2-c918-e697-2066799a31fc@redhat.com \
--to=labbott@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmoore@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=torvalds@linux-foundation.org \
--cc=trnka@scm.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