From: ebiederm@xmission.com (Eric W. Biederman) To: Linux Containers <containers@lists.linux-foundation.org> Subject: Per user rlimits Date: Fri, 28 Aug 2020 14:25:55 -0500 [thread overview] Message-ID: <87imd2incs.fsf@x220.int.ebiederm.org> (raw) Just to scope how much work it would be to fix rlimits so they are not a problem for user namespaces I took a quick survey. The rlimits can be found in include/uapi/asm-generic/resource.h There are a total of 16 rlimits. There are only 4 rlimits that are enforced at anything other than process granularity. RLIMIT_NPROC RLIMIT_MEMLOCK RLIMIT_SIGPENDING RLIMIT_MSGQUEUE So it should not be difficult to fix those rlimits. I think the implementation of RLIMIT_MEMLOCK is highly suspect, and might be worth reexamining, as RLMIT_MEMLOCK it interpreted differently in different contexts. For the limit there is mm->locked_vm, user->lock_vm, and user->locked_shm. Eric _______________________________________________ Containers mailing list Containers@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/containers
next reply other threads:[~2020-08-28 19:29 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-28 19:25 Eric W. Biederman [this message] 2020-08-28 20:33 ` Sargun Dhillon 2020-08-31 8:09 ` Aleksa Sarai 2020-08-31 8:12 ` Aleksa Sarai 2020-08-31 13:35 ` Eric W. Biederman
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=87imd2incs.fsf@x220.int.ebiederm.org \ --to=ebiederm@xmission.com \ --cc=containers@lists.linux-foundation.org \ --subject='Re: Per user rlimits' \ /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
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).