Skip to contentSkip to conversation

taskstats: Fix CGROUPSTATS_TYPE_CGROUP_STATS having same value as TASKSTATS_TYPE_PID

RFC PATCH In review Nikanth Karthikesan 2 participants 8 messages Jul 13, 2009 – Jul 14, 2009

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

RFC PATCH 1/1 taskstats: Fix CGROUPSTATS_TYPE_CGROUP_STATS having same value as TASKSTATS_TYPE_PID

Hi

Currently we never get message from kernel to userspace of type TASKSTATS_TYPE_PID. Otherwise this could have been spotted earlier.

I was trying to add a new taskstat command that would return response of type TASKSTATS_TYPE_PID.

Having the same values would restrict one not to use the same netlink socket for a command that would return response of type TASKSTATS_TYPE_PID and the CGROUPSTATS_CMD_GET command.

Should we fix it by using values after __TASKSTATS_TYPE_MAX.

Changing this now might break pre-built binaries. Or is this intended, and the application is not supposed to use CGROUPSTATS and TASKSTATS on the same socket?

Thanks
Nikanth

Currently we never get message from kernel to userspace of type TASKSTATS_TYPE_PID. Otherwise this could have been spotted earlier. Having the values in the same range would restrict one not to use the same netlink socket for a command that would return response of type TASKSTATS_TYPE_PID and the CGROUPSTATS_CMD_GET command. Fix it by using values after __TASKSTATS_TYPE_MAX.

---

include/linux/cgroupstats.h +1 -1
index 3753c33..87b31f0 100644
@@ -53,7 +53,7 @@ enum {
 #define CGROUPSTATS_CMD_MAX (__CGROUPSTATS_CMD_MAX - 1)
 
 enum {
-	CGROUPSTATS_TYPE_UNSPEC = 0,	/* Reserved */
+	CGROUPSTATS_TYPE_UNSPEC = __TASKSTATS_TYPE_MAX,	/* Reserved */
 	CGROUPSTATS_TYPE_CGROUP_STATS,	/* contains name + stats */
 	__CGROUPSTATS_TYPE_MAX,
 };
Reviewed-by on v1 1/1
#1 lore raw
Quoted 12 lines · Nikanth Karthikesan

Hi

Currently we never get message from kernel to userspace of type TASKSTATS_TYPE_PID. Otherwise this could have been spotted earlier.

I was trying to add a new taskstat command that would return response of type TASKSTATS_TYPE_PID.

Having the same values would restrict one not to use the same netlink socket for a command that would return response of type TASKSTATS_TYPE_PID and the CGROUPSTATS_CMD_GET command.

Quoted 6 lines

Should we fix it by using values after __TASKSTATS_TYPE_MAX.

Changing this now might break pre-built binaries. Or is this intended, and the application is not supposed to use CGROUPSTATS and TASKSTATS on the same socket?

Ideally they are supposed to be on different sockets, but nothing really is hard and fast in terms of rules.

Quoted 21 lines

Thanks
Nikanth

Currently we never get message from kernel to userspace of type TASKSTATS_TYPE_PID. Otherwise this could have been spotted earlier. Having the values in the same range would restrict one not to use the same netlink socket for a command that would return response of type TASKSTATS_TYPE_PID and the CGROUPSTATS_CMD_GET command. Fix it by using values after __TASKSTATS_TYPE_MAX.

---

include/linux/cgroupstats.h +0 -0
index 3753c33..87b31f0 100644

include/linux/cgroupstats.h enum { · line 59

Quoted 8 lines
include/linux/cgroupstats.h +1 -1
@@ -53,7 +53,7 @@ enum {
 #define CGROUPSTATS_CMD_MAX (__CGROUPSTATS_CMD_MAX - 1)
 
 enum {
-	CGROUPSTATS_TYPE_UNSPEC = 0,	/* Reserved */
+	CGROUPSTATS_TYPE_UNSPEC = __TASKSTATS_TYPE_MAX,	/* Reserved */
 	CGROUPSTATS_TYPE_CGROUP_STATS,	/* contains name + stats */
 	__CGROUPSTATS_TYPE_MAX,
 };

This seems like the correct fix

Signature · 1 line
	Balbir
#2 lore raw
Quoted 13 lines · On Monday 13 July 2009 19:11:58 Balbir Singh wrote:
Quoted 12 lines · Nikanth Karthikesan

Hi

Currently we never get message from kernel to userspace of type TASKSTATS_TYPE_PID. Otherwise this could have been spotted earlier.

I was trying to add a new taskstat command that would return response of type TASKSTATS_TYPE_PID.

Having the same values would restrict one not to use the same netlink socket for a command that would return response of type TASKSTATS_TYPE_PID and the CGROUPSTATS_CMD_GET command.

Quoted 9 lines
Quoted 5 lines

Should we fix it by using values after __TASKSTATS_TYPE_MAX.

Changing this now might break pre-built binaries. Or is this intended, and the application is not supposed to use CGROUPSTATS and TASKSTATS on the same socket?

Ideally they are supposed to be on different sockets, but nothing really is hard and fast in terms of rules.

IMHO, If we are adding CGROUPSTATS_CMD_GET to the same netlink family of TASKSTATS, we should allow both the commands in the same socket.

Quoted 32 lines
Quoted 21 lines

Thanks
Nikanth

Currently we never get message from kernel to userspace of type TASKSTATS_TYPE_PID. Otherwise this could have been spotted earlier. Having the values in the same range would restrict one not to use the same netlink socket for a command that would return response of type TASKSTATS_TYPE_PID and the CGROUPSTATS_CMD_GET command. Fix it by using values after
__TASKSTATS_TYPE_MAX.

---

include/linux/cgroupstats.h +0 -0
index 3753c33..87b31f0 100644

include/linux/cgroupstats.h enum { · line 59

Quoted 8 lines
include/linux/cgroupstats.h +1 -1
@@ -53,7 +53,7 @@ enum {
 #define CGROUPSTATS_CMD_MAX (__CGROUPSTATS_CMD_MAX - 1)
 
 enum {
-	CGROUPSTATS_TYPE_UNSPEC = 0,	/* Reserved */
+	CGROUPSTATS_TYPE_UNSPEC = __TASKSTATS_TYPE_MAX,	/* Reserved */
 	CGROUPSTATS_TYPE_CGROUP_STATS,	/* contains name + stats */
 	__CGROUPSTATS_TYPE_MAX,
 };

This seems like the correct fix

Quoted 1 line

But this would break applications every time a new item is added to the enums in taskstat.h

The correct fix would be to add all the CGROUPSTATS_* enums, as part of the same enum in taskstat.h. So that when new members are added to enum's in taskstat.h, the cgroup stat enum's values won't change and applications need not be re-built. If you agree, I would send a patch to do that.

Thanks
Nikanth

#3 lore raw
Quoted 59 lines · Nikanth Karthikesan
Quoted 13 lines · On Monday 13 July 2009 19:11:58 Balbir Singh wrote:
Quoted 12 lines · Nikanth Karthikesan

Hi

Currently we never get message from kernel to userspace of type TASKSTATS_TYPE_PID. Otherwise this could have been spotted earlier.

I was trying to add a new taskstat command that would return response of type TASKSTATS_TYPE_PID.

Having the same values would restrict one not to use the same netlink socket for a command that would return response of type TASKSTATS_TYPE_PID and the CGROUPSTATS_CMD_GET command.

Quoted 9 lines
Quoted 5 lines

Should we fix it by using values after __TASKSTATS_TYPE_MAX.

Changing this now might break pre-built binaries. Or is this intended, and the application is not supposed to use CGROUPSTATS and TASKSTATS on the same socket?

Ideally they are supposed to be on different sockets, but nothing really is hard and fast in terms of rules.

IMHO, If we are adding CGROUPSTATS_CMD_GET to the same netlink family of TASKSTATS, we should allow both the commands in the same socket.

Quoted 32 lines
Quoted 21 lines

Thanks
Nikanth

Currently we never get message from kernel to userspace of type TASKSTATS_TYPE_PID. Otherwise this could have been spotted earlier. Having the values in the same range would restrict one not to use the same netlink socket for a command that would return response of type TASKSTATS_TYPE_PID and the CGROUPSTATS_CMD_GET command. Fix it by using values after
__TASKSTATS_TYPE_MAX.

---

include/linux/cgroupstats.h +0 -0
index 3753c33..87b31f0 100644

include/linux/cgroupstats.h enum { · line 59

Quoted 8 lines
include/linux/cgroupstats.h +1 -1
@@ -53,7 +53,7 @@ enum {
 #define CGROUPSTATS_CMD_MAX (__CGROUPSTATS_CMD_MAX - 1)
 
 enum {
-	CGROUPSTATS_TYPE_UNSPEC = 0,	/* Reserved */
+	CGROUPSTATS_TYPE_UNSPEC = __TASKSTATS_TYPE_MAX,	/* Reserved */
 	CGROUPSTATS_TYPE_CGROUP_STATS,	/* contains name + stats */
 	__CGROUPSTATS_TYPE_MAX,
 };

This seems like the correct fix

Quoted 5 lines
Quoted 1 line

But this would break applications every time a new item is added to the enums in taskstat.h

Yes, correct and the expectation, we will bump the version number (see version field) or ignore the fix and send a strong recommendation that we should use different sockets for cgroupstats and taskstats.

Quoted 5 lines

The correct fix would be to add all the CGROUPSTATS_* enums, as part of the same enum in taskstat.h. So that when new members are added to enum's in taskstat.h, the cgroup stat enum's values won't change and applications need not be re-built. If you agree, I would send a patch to do that.

I wanted to keep the separate to avoid #ifdef's around the code. One other generic fix would be to use different starting bases. We could for example use a bit (say bit 63) to indicate the type - taskstats or cgroupstats, but we might be too late for that.

Please remember to bump the version field, lets try your suggested approach of integration and if that can be done cleanly, I have no objection.

Signature · 1 line
	Balbir
#4 lore raw
Quoted 74 lines · On Monday 13 July 2009 21:23:10 Balbir Singh wrote:
Quoted 58 lines · Nikanth Karthikesan
Quoted 13 lines · On Monday 13 July 2009 19:11:58 Balbir Singh wrote:
Quoted 12 lines · Nikanth Karthikesan

Hi

Currently we never get message from kernel to userspace of type TASKSTATS_TYPE_PID. Otherwise this could have been spotted earlier.

I was trying to add a new taskstat command that would return response of type TASKSTATS_TYPE_PID.

Having the same values would restrict one not to use the same netlink socket for a command that would return response of type TASKSTATS_TYPE_PID and the CGROUPSTATS_CMD_GET command.

Quoted 8 lines
Quoted 5 lines

Should we fix it by using values after __TASKSTATS_TYPE_MAX.

Changing this now might break pre-built binaries. Or is this intended, and the application is not supposed to use CGROUPSTATS and TASKSTATS on the same socket?

Ideally they are supposed to be on different sockets, but nothing really is hard and fast in terms of rules.

IMHO, If we are adding CGROUPSTATS_CMD_GET to the same netlink family of TASKSTATS, we should allow both the commands in the same socket.

Quoted 32 lines
Quoted 21 lines

Thanks
Nikanth

Currently we never get message from kernel to userspace of type TASKSTATS_TYPE_PID. Otherwise this could have been spotted earlier. Having the values in the same range would restrict one not to use the same netlink socket for a command that would return response of type TASKSTATS_TYPE_PID and the CGROUPSTATS_CMD_GET command. Fix it by using values after
__TASKSTATS_TYPE_MAX.

---

(quoted diff) +0 -0

b/include/linux/cgroupstats.h index 3753c33..87b31f0 100644

include/linux/cgroupstats.h enum { · line 59

Quoted 8 lines
include/linux/cgroupstats.h +1 -1
@@ -53,7 +53,7 @@ enum {
 #define CGROUPSTATS_CMD_MAX (__CGROUPSTATS_CMD_MAX - 1)
 
 enum {
-	CGROUPSTATS_TYPE_UNSPEC = 0,	/* Reserved */
+	CGROUPSTATS_TYPE_UNSPEC = __TASKSTATS_TYPE_MAX,	/* Reserved */
 	CGROUPSTATS_TYPE_CGROUP_STATS,	/* contains name + stats */
 	__CGROUPSTATS_TYPE_MAX,
 };

This seems like the correct fix

Quoted 4 lines
Quoted 1 line

But this would break applications every time a new item is added to the enums in taskstat.h

Yes, correct and the expectation, we will bump the version number (see version field) or ignore the fix and send a strong recommendation that we should use different sockets for cgroupstats and taskstats.

Quoted 5 lines

The correct fix would be to add all the CGROUPSTATS_* enums, as part of the same enum in taskstat.h. So that when new members are added to enum's in taskstat.h, the cgroup stat enum's values won't change and applications need not be re-built. If you agree, I would send a patch to do that.

Quoted 8 lines

I wanted to keep the separate to avoid #ifdef's around the code. One other generic fix would be to use different starting bases. We could for example use a bit (say bit 63) to indicate the type - taskstats or cgroupstats, but we might be too late for that.

Please remember to bump the version field, lets try your suggested approach of integration and if that can be done cleanly, I have no objection.

I have posted[0] it with subject, "[PATCH] taskstats: Unify cgroupstats.h with taskstats.h and use a single nla_policy". Please do review it.

Thanks
Nikanth

[0] http://lkml.org/lkml/2009/7/13/189

#5 lore raw
In reply to Balbir Singh
Quoted 45 lines · On Monday 13 July 2009 19:11:58 Balbir Singh wrote:
Quoted 12 lines · Nikanth Karthikesan

Hi

Currently we never get message from kernel to userspace of type TASKSTATS_TYPE_PID. Otherwise this could have been spotted earlier.

I was trying to add a new taskstat command that would return response of type TASKSTATS_TYPE_PID.

Having the same values would restrict one not to use the same netlink socket for a command that would return response of type TASKSTATS_TYPE_PID and the CGROUPSTATS_CMD_GET command.

Quoted 5 lines

Should we fix it by using values after __TASKSTATS_TYPE_MAX.

Changing this now might break pre-built binaries. Or is this intended, and the application is not supposed to use CGROUPSTATS and TASKSTATS on the same socket?

Ideally they are supposed to be on different sockets, but nothing really is hard and fast in terms of rules.

Quoted 23 lines

Thanks
Nikanth

Currently we never get message from kernel to userspace of type TASKSTATS_TYPE_PID. Otherwise this could have been spotted earlier. Having the values in the same range would restrict one not to use the same netlink socket for a command that would return response of type TASKSTATS_TYPE_PID and the CGROUPSTATS_CMD_GET command. Fix it by using values after
__TASKSTATS_TYPE_MAX.

---

include/linux/cgroupstats.h +0 -0
index 3753c33..87b31f0 100644
@@ -53,7 +53,7 @@ enum {
 #define CGROUPSTATS_CMD_MAX (__CGROUPSTATS_CMD_MAX - 1)
 
Quoted 7 lines

include/linux/cgroupstats.h enum { · line 59

Quoted 6 lines
include/linux/cgroupstats.h +1 -1
 enum {
-	CGROUPSTATS_TYPE_UNSPEC = 0,	/* Reserved */
+	CGROUPSTATS_TYPE_UNSPEC = __TASKSTATS_TYPE_MAX,	/* Reserved */
 	CGROUPSTATS_TYPE_CGROUP_STATS,	/* contains name + stats */
 	__CGROUPSTATS_TYPE_MAX,
 };

Also this would unnecessarily increase the value of __CGROUPSTATS_TYPE_MAX. So, please dont take this patch. :) I would send a better fix, soon.

Thanks
Nikanth

#6 lore raw
Quoted 54 lines · Nikanth Karthikesan
Quoted 45 lines · On Monday 13 July 2009 19:11:58 Balbir Singh wrote:
Quoted 12 lines · Nikanth Karthikesan

Hi

Currently we never get message from kernel to userspace of type TASKSTATS_TYPE_PID. Otherwise this could have been spotted earlier.

I was trying to add a new taskstat command that would return response of type TASKSTATS_TYPE_PID.

Having the same values would restrict one not to use the same netlink socket for a command that would return response of type TASKSTATS_TYPE_PID and the CGROUPSTATS_CMD_GET command.

Quoted 5 lines

Should we fix it by using values after __TASKSTATS_TYPE_MAX.

Changing this now might break pre-built binaries. Or is this intended, and the application is not supposed to use CGROUPSTATS and TASKSTATS on the same socket?

Ideally they are supposed to be on different sockets, but nothing really is hard and fast in terms of rules.

Quoted 23 lines

Thanks
Nikanth

Currently we never get message from kernel to userspace of type TASKSTATS_TYPE_PID. Otherwise this could have been spotted earlier. Having the values in the same range would restrict one not to use the same netlink socket for a command that would return response of type TASKSTATS_TYPE_PID and the CGROUPSTATS_CMD_GET command. Fix it by using values after
__TASKSTATS_TYPE_MAX.

---

include/linux/cgroupstats.h +0 -0
index 3753c33..87b31f0 100644
@@ -53,7 +53,7 @@ enum {
 #define CGROUPSTATS_CMD_MAX (__CGROUPSTATS_CMD_MAX - 1)
 
Quoted 7 lines

include/linux/cgroupstats.h enum { · line 59

Quoted 6 lines
include/linux/cgroupstats.h +1 -1
 enum {
-	CGROUPSTATS_TYPE_UNSPEC = 0,	/* Reserved */
+	CGROUPSTATS_TYPE_UNSPEC = __TASKSTATS_TYPE_MAX,	/* Reserved */
 	CGROUPSTATS_TYPE_CGROUP_STATS,	/* contains name + stats */
 	__CGROUPSTATS_TYPE_MAX,
 };
Quoted 3 lines

Also this would unnecessarily increase the value of __CGROUPSTATS_TYPE_MAX. So, please dont take this patch. :) I would send a better fix, soon.

Yes, agreed, but ideally __CGROUPSTATS_TYPE_MAX represents the max of taskstats and cgroupstats so it should be OK in principle, but lets try another approach to fix this.

Signature · 1 line
	Balbir
#7 lore raw

PATCH 1/1 taskstats: Unify cgroupstats.h with taskstats.h and use a single nla_policy

Currently we never get message from kernel to userspace of type TASKSTATS_TYPE_PID. Having the values in the same range would restrict one not to use the same netlink socket for a command that would return response of type TASKSTATS_TYPE_PID and the CGROUPSTATS_CMD_GET command.

Change it by using the same set of types and attributes for both TASKSTATS_CMD_NEW/GET and CGROUPSTATS_CMD_GET/NEW by using the same nla_policy.

Unify linux/cgroupstats.h with linux/taskstat.h

Bump the taskstat version while doing so.

---

Documentation/accounting/getdelays.c +1 -2
index aa73e72..ffac484 100644
@@ -25,7 +25,6 @@
 
 #include <linux/genetlink.h>
 #include <linux/taskstats.h>
-#include <linux/cgroupstats.h>
 
 /*
  * Generic macros for dealing with netlink sockets. Might be duplicated
@@ -133,7 +132,7 @@ int send_cmd(int sd, __u16 nlmsg_type, __u32 nlmsg_pid,
 	msg.n.nlmsg_seq = 0;
 	msg.n.nlmsg_pid = nlmsg_pid;
 	msg.g.cmd = genl_cmd;
-	msg.g.version = 0x1;
+	msg.g.version = 0x2;
 	na = (struct nlattr *) GENLMSG_DATA(&msg);
 	na->nla_type = nla_type;
 	na->nla_len = nla_len + 1 + NLA_HDRLEN;
include/linux/cgroup.h +1 -1
index 665fa70..dd7c675 100644
@@ -12,7 +12,7 @@
 #include <linux/cpumask.h>
 #include <linux/nodemask.h>
 #include <linux/rcupdate.h>
-#include <linux/cgroupstats.h>
+#include <linux/taskstats.h>
 #include <linux/prio_heap.h>
 #include <linux/rwsem.h>
 #include <linux/idr.h>
include/linux/cgroupstats.h deleted +0 -71

71 lines not on this page · raw message

include/linux/taskstats.h +24 -1
index 341dddb..cba4594 100644
@@ -165,6 +165,24 @@ struct taskstats {
 	__u64	freepages_delay_total;
 };
 
+/*
+ * Data shared between user space and kernel space on a per cgroup
+ * basis. This data is shared using taskstats.
+ *
+ * Most of these states are derived by looking at the task->state value
+ * For the nr_io_wait state, a flag in the delay accounting structure
+ * indicates that the task is waiting on IO
+ *
+ * Each member is aligned to a 8 byte boundary.
+ */
+struct cgroupstats {
+	__u64	nr_sleeping;		/* Number of tasks sleeping */
+	__u64	nr_running;		/* Number of tasks running */
+	__u64	nr_stopped;		/* Number of tasks in stopped state */
+	__u64	nr_uninterruptible;	/* Number of tasks in uninterruptible */
+					/* state */
+	__u64	nr_io_wait;		/* Number of tasks waiting on IO */
+};
 
 /*
  * Commands sent from userspace
@@ -176,6 +194,9 @@ enum {
 	TASKSTATS_CMD_UNSPEC = 0,	/* Reserved */
 	TASKSTATS_CMD_GET,		/* user->kernel request/get-response */
 	TASKSTATS_CMD_NEW,		/* kernel->user event */
+	CGROUPSTATS_CMD_GET,		/* user->kernel request/get-response */
+					/* for cgroup statistics */
+	CGROUPSTATS_CMD_NEW,		/* kernel->user event for cgroups */
 	__TASKSTATS_CMD_MAX,
 };
 
@@ -188,6 +209,7 @@ enum {
 	TASKSTATS_TYPE_STATS,		/* taskstats structure */
 	TASKSTATS_TYPE_AGGR_PID,	/* contains pid + stats */
 	TASKSTATS_TYPE_AGGR_TGID,	/* contains tgid + stats */
+	CGROUPSTATS_TYPE_CGROUP_STATS,	/* contains cgroup name + stats */
 	__TASKSTATS_TYPE_MAX,
 };
 
@@ -199,6 +221,7 @@ enum {
 	TASKSTATS_CMD_ATTR_TGID,
 	TASKSTATS_CMD_ATTR_REGISTER_CPUMASK,
 	TASKSTATS_CMD_ATTR_DEREGISTER_CPUMASK,
+	CGROUPSTATS_CMD_ATTR_FD,
 	__TASKSTATS_CMD_ATTR_MAX,
 };
 
@@ -207,6 +230,6 @@ enum {
 /* NETLINK_GENERIC related info */
 
 #define TASKSTATS_GENL_NAME	"TASKSTATS"
-#define TASKSTATS_GENL_VERSION	0x1
+#define TASKSTATS_GENL_VERSION	0x2
 
 #endif /* _LINUX_TASKSTATS_H */
kernel/cgroup.c +1 -1
index 3737a68..94bee03 100644
@@ -43,7 +43,7 @@
 #include <linux/sort.h>
 #include <linux/kmod.h>
 #include <linux/delayacct.h>
-#include <linux/cgroupstats.h>
+#include <linux/taskstats.h>
 #include <linux/hash.h>
 #include <linux/namei.h>
 #include <linux/smp_lock.h>
kernel/taskstats.c +4 -8
index 888adbc..448caba 100644
@@ -22,7 +22,6 @@
 #include <linux/delayacct.h>
 #include <linux/cpumask.h>
 #include <linux/percpu.h>
-#include <linux/cgroupstats.h>
 #include <linux/cgroup.h>
 #include <linux/fs.h>
 #include <linux/file.h>
@@ -46,15 +45,12 @@ static struct genl_family family = {
 	.maxattr	= TASKSTATS_CMD_ATTR_MAX,
 };
 
-static struct nla_policy taskstats_cmd_get_policy[TASKSTATS_CMD_ATTR_MAX+1]
+static struct nla_policy policy[TASKSTATS_CMD_ATTR_MAX+1]
 __read_mostly = {
 	[TASKSTATS_CMD_ATTR_PID]  = { .type = NLA_U32 },
 	[TASKSTATS_CMD_ATTR_TGID] = { .type = NLA_U32 },
 	[TASKSTATS_CMD_ATTR_REGISTER_CPUMASK] = { .type = NLA_STRING },
-	[TASKSTATS_CMD_ATTR_DEREGISTER_CPUMASK] = { .type = NLA_STRING },};
-
-static struct nla_policy
-cgroupstats_cmd_get_policy[CGROUPSTATS_CMD_ATTR_MAX+1] __read_mostly = {
+	[TASKSTATS_CMD_ATTR_DEREGISTER_CPUMASK] = { .type = NLA_STRING },
 	[CGROUPSTATS_CMD_ATTR_FD] = { .type = NLA_U32 },
 };
 
@@ -582,13 +578,13 @@ err:
 static struct genl_ops taskstats_ops = {
 	.cmd		= TASKSTATS_CMD_GET,
 	.doit		= taskstats_user_cmd,
-	.policy		= taskstats_cmd_get_policy,
+	.policy		= policy,
 };
 
 static struct genl_ops cgroupstats_ops = {
 	.cmd		= CGROUPSTATS_CMD_GET,
 	.doit		= cgroupstats_user_cmd,
-	.policy		= cgroupstats_cmd_get_policy,
+	.policy		= policy,
 };
 
 /* Needed early in initialization */