From: Andy Lutomirski <luto@kernel.org>
To: Topi Miettinen <toiwoton@gmail.com>, linux-kernel@vger.kernel.org
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Kees Cook <keescook@chromium.org>,
Cyrill Gorcunov <gorcunov@openvz.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
John Stultz <john.stultz@linaro.org>,
Janis Danisevskis <jdanis@google.com>,
Calvin Owens <calvinowens@fb.com>, Jann Horn <jann@thejh.net>,
"open list:FILESYSTEMS (VFS and infrastructure)"
<linux-fsdevel@vger.kernel.org>
Subject: Re: [RFC 05/18] limits: track and present RLIMIT_NOFILE actual max
Date: Mon, 13 Jun 2016 13:40:09 -0700 [thread overview]
Message-ID: <887b928a-87f3-46aa-cfd3-d962fe40b85f@kernel.org> (raw)
In-Reply-To: <1465847065-3577-6-git-send-email-toiwoton@gmail.com>
On 06/13/2016 12:44 PM, Topi Miettinen wrote:
> Track maximum number of files for the process, present current maximum
> in /proc/self/limits.
The core part should be its own patch.
Also, you have this weirdly named (and racy!) function bump_rlimit.
Wouldn't this be nicer if you taught the rlimit code to track the
*current* usage generically and to derive the max usage from that?
> diff --git a/fs/proc/base.c b/fs/proc/base.c
> index a11eb71..227997b 100644
> --- a/fs/proc/base.c
> +++ b/fs/proc/base.c
> @@ -630,8 +630,8 @@ static int proc_pid_limits(struct seq_file *m, struct pid_namespace *ns,
> /*
> * print the file header
> */
> - seq_printf(m, "%-25s %-20s %-20s %-10s\n",
> - "Limit", "Soft Limit", "Hard Limit", "Units");
> + seq_printf(m, "%-25s %-20s %-20s %-10s %-20s\n",
> + "Limit", "Soft Limit", "Hard Limit", "Units", "Max");
What existing programs, if any, does this break?
>
> for (i = 0; i < RLIM_NLIMITS; i++) {
> if (rlim[i].rlim_cur == RLIM_INFINITY)
> @@ -647,9 +647,11 @@ static int proc_pid_limits(struct seq_file *m, struct pid_namespace *ns,
> seq_printf(m, "%-20lu ", rlim[i].rlim_max);
>
> if (lnames[i].unit)
> - seq_printf(m, "%-10s\n", lnames[i].unit);
> + seq_printf(m, "%-10s", lnames[i].unit);
> else
> - seq_putc(m, '\n');
> + seq_printf(m, "%-10s", "");
> + seq_printf(m, "%-20lu\n",
> + task->signal->rlim_curmax[i]);
> }
>
> return 0;
> diff --git a/include/linux/sched.h b/include/linux/sched.h
> index 9c48a08..0150380 100644
> --- a/include/linux/sched.h
> +++ b/include/linux/sched.h
> @@ -782,6 +782,7 @@ struct signal_struct {
> * have no need to disable irqs.
> */
> struct rlimit rlim[RLIM_NLIMITS];
> + unsigned long rlim_curmax[RLIM_NLIMITS];
>
> #ifdef CONFIG_BSD_PROCESS_ACCT
> struct pacct_struct pacct; /* per-process accounting information */
> @@ -3376,6 +3377,12 @@ static inline unsigned long rlimit_max(unsigned int limit)
> return task_rlimit_max(current, limit);
> }
>
> +static inline void bump_rlimit(unsigned int limit, unsigned long r)
> +{
> + if (READ_ONCE(current->signal->rlim_curmax[limit]) < r)
> + current->signal->rlim_curmax[limit] = r;
> +}
> +
> #ifdef CONFIG_CPU_FREQ
> struct update_util_data {
> void (*func)(struct update_util_data *data,
>
next prev parent reply other threads:[~2016-06-13 20:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1465847065-3577-1-git-send-email-toiwoton@gmail.com>
2016-06-13 19:44 ` [RFC 01/18] capabilities: track actually used capabilities Topi Miettinen
2016-06-13 20:32 ` Andy Lutomirski
2016-06-13 20:45 ` Topi Miettinen
2016-06-13 21:12 ` Andy Lutomirski
2016-06-13 21:48 ` Topi Miettinen
2016-06-13 19:44 ` [RFC 05/18] limits: track and present RLIMIT_NOFILE actual max Topi Miettinen
2016-06-13 20:40 ` Andy Lutomirski [this message]
2016-06-13 21:13 ` Topi Miettinen
2016-06-13 21:16 ` Andy Lutomirski
2016-06-14 15:21 ` Topi Miettinen
2016-06-13 19:44 ` [RFC 07/18] limits: track RLIMIT_FSIZE " Topi Miettinen
2016-06-13 19:44 ` [RFC 08/18] limits: track RLIMIT_DATA " Topi Miettinen
2016-06-13 19:44 ` [RFC 09/18] limits: track RLIMIT_CORE " Topi Miettinen
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=887b928a-87f3-46aa-cfd3-d962fe40b85f@kernel.org \
--to=luto@kernel.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=calvinowens@fb.com \
--cc=gorcunov@openvz.org \
--cc=jann@thejh.net \
--cc=jdanis@google.com \
--cc=john.stultz@linaro.org \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=toiwoton@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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).