mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Kosina <jikos@kernel.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: tip-bot for Michal Hocko <tipbot@zytor.com>,
	linux-tip-commits@vger.kernel.org, torvalds@linux-foundation.org,
	mingo@kernel.org, hpa@zytor.com, mhocko@suse.com,
	tglx@linutronix.de, davej@codemonkey.org.uk,
	peterz@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [tip:x86/mm] x86/mmap, ASLR: Do not treat unlimited-stack tasks as legacy mmap
Date: Wed, 28 Jun 2017 11:40:06 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LSU.2.20.1706281134380.30709@cbobk.fhfr.pm> (raw)
In-Reply-To: <20170627142215.GA5645@redhat.com>

On Tue, 27 Jun 2017, Oleg Nesterov wrote:

> Perhaps it makes sense to reset RLIMITs on suid exec (say, if 
> bprm->per_clear is not zero) ? Yes, it is not clear how should we define 
> SANE_RLIMITS_FOR_SUID, and this should probably depend on sysctl, etc.

Hmm, this should be an userspace-defined policy. On a 'standard' 
(PAM-based) system, I think a sane expectation would be to get the same 
limits as the ones enforced by pam_limits configuration, but syncing those 
with kernel feels awkward.

Thanks,

-- 
Jiri Kosina
SUSE Labs

  reply	other threads:[~2017-06-28  9:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14  8:22 [RFC PATCH] mmap, aslr: do not enforce legacy mmap on unlimited stacks Michal Hocko
2017-06-23  8:46 ` Michal Hocko
2017-06-23 14:02 ` [tip:x86/mm] x86/mmap, ASLR: Do not treat unlimited-stack tasks as legacy mmap tip-bot for Michal Hocko
2017-06-23 14:54   ` Oleg Nesterov
2017-06-27  8:00     ` Jiri Kosina
2017-06-27 14:22       ` Oleg Nesterov
2017-06-28  9:40         ` Jiri Kosina [this message]
2017-06-23 20:35   ` Jiri Kosina
2017-06-24  6:43   ` tip-bot for Michal Hocko

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=alpine.LSU.2.20.1706281134380.30709@cbobk.fhfr.pm \
    --to=jikos@kernel.org \
    --cc=davej@codemonkey.org.uk \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mhocko@suse.com \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=tipbot@zytor.com \
    --cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®