From: Clifford Wolf <clifford@clifford.at>
To: lkml <linux-kernel@vger.kernel.org>
Subject: [PATCH] rlim in proc/<pid>/status
Date: Tue, 15 Jan 2008 11:06:31 +0100 [thread overview]
Message-ID: <20080115100631.GA13394@clifford.at> (raw)
Hi,
because I needed it already twice in two different projects this week: the
following patch adds rlim (ulimits) output to /proc/<pid>/status.
Please let me know if there is another (already existing) way of accessing
this information easy (i.e. connecting with gdb to the process in question
and 'injecting' a getrlimit() call does not count.. ;-).
yours,
- clifford
Signed-off-by: Clifford Wolf <clifford@clifford.at>
--- linux/fs/proc/array.c (revision 757)
+++ linux/fs/proc/array.c (working copy)
@@ -239,6 +239,55 @@
}
}
+static char *rlim_names[RLIM_NLIMITS] = {
+ [RLIMIT_CPU] = "CPU",
+ [RLIMIT_FSIZE] = "FSize",
+ [RLIMIT_DATA] = "Data",
+ [RLIMIT_STACK] = "Stack",
+ [RLIMIT_CORE] = "Core",
+ [RLIMIT_RSS] = "RSS",
+ [RLIMIT_NPROC] = "NProc",
+ [RLIMIT_NOFILE] = "NoFile",
+ [RLIMIT_MEMLOCK] = "MemLock",
+ [RLIMIT_AS] = "AddrSpace",
+ [RLIMIT_LOCKS] = "Locks",
+ [RLIMIT_SIGPENDING] = "SigPending",
+ [RLIMIT_MSGQUEUE] = "MsgQueue",
+ [RLIMIT_NICE] = "Nice",
+ [RLIMIT_RTPRIO] = "RTPrio"
+};
+
+static inline char *task_rlim(struct task_struct *p, char *buffer)
+{
+ unsigned long flags;
+ struct rlimit rlim[RLIM_NLIMITS];
+ int i;
+
+ rcu_read_lock();
+ if (lock_task_sighand(p, &flags)) {
+ for (i=0; i<RLIM_NLIMITS; i++)
+ rlim[i] = p->signal->rlim[i];
+ }
+ rcu_read_unlock();
+
+ for (i=0; i<RLIM_NLIMITS; i++) {
+ if (rlim_names[i])
+ buffer += sprintf(buffer, "Rlim%s:\t", rlim_names[i]);
+ else
+ buffer += sprintf(buffer, "Rlim%d:\t", i);
+ if (rlim[i].rlim_cur != ~0)
+ buffer += sprintf(buffer, "%lu\t", rlim[i].rlim_cur);
+ else
+ buffer += sprintf(buffer, "-\t");
+ if (rlim[i].rlim_max != ~0)
+ buffer += sprintf(buffer, "%lu\n", rlim[i].rlim_max);
+ else
+ buffer += sprintf(buffer, "-\n");
+ }
+
+ return buffer;
+}
+
static inline char *task_sig(struct task_struct *p, char *buffer)
{
unsigned long flags;
@@ -310,6 +359,7 @@
buffer = task_mem(mm, buffer);
mmput(mm);
}
+ buffer = task_rlim(task, buffer);
buffer = task_sig(task, buffer);
buffer = task_cap(task, buffer);
buffer = cpuset_task_status_allowed(task, buffer);
--
[..] If it still doesn't work, re-write it in assembler. This won't fix the
bug, but it will make sure no one else finds it and makes you look bad.
next reply other threads:[~2008-01-15 10:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 10:06 Clifford Wolf [this message]
2008-01-15 10:47 ` KOSAKI Motohiro
2008-01-15 12:15 ` Clifford Wolf
2008-01-15 20:36 ` [PATCH] " serge
2008-01-16 7:03 ` [PATCH] rlim in proc/<pid>/status (2nd rev.) Clifford Wolf
2008-01-16 7:33 ` KOSAKI Motohiro
2008-01-16 10:04 ` Clifford Wolf
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=20080115100631.GA13394@clifford.at \
--to=clifford@clifford.at \
--cc=linux-kernel@vger.kernel.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®