| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20111222132415.GS12782@moon>
Date: Thu, 22 Dec 2011 17:24:15 +0400
From: Cyrill Gorcunov <gorcunov@...il.com>
To: linux-kernel@...r.kernel.org
Cc: Pavel Emelyanov <xemul@...allels.com>,
Glauber Costa <glommer@...allels.com>,
Andi Kleen <andi@...stfloor.org>, Tejun Heo <tj@...nel.org>,
Matt Helsley <matthltc@...ibm.com>,
Pekka Enberg <penberg@...nel.org>,
Eric Dumazet <eric.dumazet@...il.com>,
Vasiliy Kulikov <segoon@...nwall.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [patch 0/4] kernel generic object IDs series
On Thu, Dec 22, 2011 at 04:56:39PM +0400, Cyrill Gorcunov wrote:
...
>
> Any kind of comments and especially complains (!) are very appreciated!
>
> Cyrill
>
Because of "CLONE_XXX" in subject, LKML dropped the fourth patch, so I
renamed it and put it here. Sorry for inconvenince.
Cyrill
---
proc: Show IDs of objects cloned with CLONE_ in proc
An example of output is
# cat /proc/2332/objects
VM :445332486314238977
FILES :16574420397857109505
FS :7421276367695228033
SIGHAND :9517130248188834433
IO :9605099974489260945
SYSVSEM :0
each one represents an ID of appropriate resource used
by a task -- memory, signals, fs and etc.
Based-on-patch-from: Pavel Emelyanov <xemul@...allels.com>
Signed-off-by: Cyrill Gorcunov <gorcunov@...nvz.org>
CC: Glauber Costa <glommer@...allels.com>
CC: Andi Kleen <andi@...stfloor.org>
CC: Tejun Heo <tj@...nel.org>
CC: Matt Helsley <matthltc@...ibm.com>
CC: Pekka Enberg <penberg@...nel.org>
CC: Eric Dumazet <eric.dumazet@...il.com>
CC: Vasiliy Kulikov <segoon@...nwall.com>
CC: Andrew Morton <akpm@...ux-foundation.org>
---
Documentation/filesystems/proc.txt | 18 ++++++++++++++++++
fs/proc/base.c | 29 +++++++++++++++++++++++++++++
include/linux/mm.h | 6 ++++++
3 files changed, 53 insertions(+)
Index: linux-2.6.git/Documentation/filesystems/proc.txt
===================================================================
--- linux-2.6.git.orig/Documentation/filesystems/proc.txt
+++ linux-2.6.git/Documentation/filesystems/proc.txt
@@ -41,6 +41,7 @@ Table of Contents
3.5 /proc/<pid>/mountinfo - Information about mounts
3.6 /proc/<pid>/comm & /proc/<pid>/task/<tid>/comm
3.7 /proc/<pid>/ns - Information about namespaces
+ 3.8 /proc/<pid>/objects - Information about generic objects
------------------------------------------------------------------------------
@@ -1569,3 +1570,20 @@ obtained from another <pid>.
Moreover, a safe approach is to remember it as a string, since format may
change in future and id would be not a long integer value, but something
else, say SHA1/2 or even uuid encoded stream.
+
+3.8 /proc/<pid>/objects - Information about generic objects
+---------------------------------------------------------------
+
+Similar to /proc/<pid>/ns this file provide generic object ids by
+the following format (better to illustrate with example)
+
+VM :445332486300860161
+FILES :16574420397866995457
+FS :7421276367693613825
+SIGHAND :9517130248196786369
+IO :0
+SYSVSEM :0
+
+The first column is an object name, the second -- object ID number.
+As being mentioned in 3.7 one should carry them as a string to be
+on a safe side.
Index: linux-2.6.git/fs/proc/base.c
===================================================================
--- linux-2.6.git.orig/fs/proc/base.c
+++ linux-2.6.git/fs/proc/base.c
@@ -312,6 +312,32 @@ out:
return res;
}
+#ifdef CONFIG_GENERIC_OBJECT_IDS
+static int proc_pid_objs(struct task_struct *task, char * buffer)
+{
+ int ret = 0;
+
+#define SHOW_PID_OBJ(__type, __field) \
+ do { \
+ ret += sprintf(buffer + ret, "%-10s:%lu\n", \
+ #__type, \
+ gen_obj_id(task->__field, \
+ GEN_OBJ_ID_##__type)); \
+ } while (0)
+
+ SHOW_PID_OBJ(VM, mm);
+ SHOW_PID_OBJ(FILES, files);
+ SHOW_PID_OBJ(FS, fs);
+ SHOW_PID_OBJ(SIGHAND, sighand);
+ SHOW_PID_OBJ(IO, io_context);
+ SHOW_PID_OBJ(SYSVSEM, sysvsem.undo_list);
+
+#undef SHOW_PID_OBJ
+
+ return ret;
+}
+#endif
+
static int proc_pid_auxv(struct task_struct *task, char *buffer)
{
struct mm_struct *mm = mm_for_maps(task);
@@ -3172,6 +3198,9 @@ static const struct pid_entry tgid_base_
INF("syscall", S_IRUGO, proc_pid_syscall),
#endif
INF("cmdline", S_IRUGO, proc_pid_cmdline),
+#ifdef CONFIG_GENERIC_OBJECT_IDS
+ INF("objects", S_IRUGO, proc_pid_objs),
+#endif
ONE("stat", S_IRUGO, proc_tgid_stat),
ONE("statm", S_IRUGO, proc_pid_statm),
REG("maps", S_IRUGO, proc_maps_operations),
Index: linux-2.6.git/include/linux/mm.h
===================================================================
--- linux-2.6.git.orig/include/linux/mm.h
+++ linux-2.6.git/include/linux/mm.h
@@ -1643,6 +1643,12 @@ extern void copy_user_huge_page(struct p
enum {
GEN_OBJ_ID_NS,
GEN_OBJ_ID_FILE,
+ GEN_OBJ_ID_VM,
+ GEN_OBJ_ID_FILES,
+ GEN_OBJ_ID_FS,
+ GEN_OBJ_ID_SIGHAND,
+ GEN_OBJ_ID_IO,
+ GEN_OBJ_ID_SYSVSEM,
GEN_OBJ_ID_TYPES,
};
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists