cgroup: fix an off-by-one bug which may trigger BUG_ON()
authorLi Zefan <lizefan@huawei.com>
Tue, 12 Mar 2013 22:36:00 +0000 (15:36 -0700)
committerTejun Heo <tj@kernel.org>
Wed, 20 Mar 2013 14:50:04 +0000 (07:50 -0700)
The 3rd parameter of flex_array_prealloc() is the number of elements,
not the index of the last element.

The effect of the bug is, when opening cgroup.procs, a flex array will
be allocated and all elements of the array is allocated with
GFP_KERNEL flag, but the last one is GFP_ATOMIC, and if we fail to
allocate memory for it, it'll trigger a BUG_ON().

Signed-off-by: Li Zefan <lizefan@huawei.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
Cc: stable@vger.kernel.org
kernel/cgroup.c

index c7fe303b5109be475bf963559a067a1399ed237c..54689fc008f654eb45034773b13949a91a2af126 100644 (file)
@@ -2076,7 +2076,7 @@ static int cgroup_attach_proc(struct cgroup *cgrp, struct task_struct *leader)
        if (!group)
                return -ENOMEM;
        /* pre-allocate to guarantee space while iterating in rcu read-side. */
-       retval = flex_array_prealloc(group, 0, group_size - 1, GFP_KERNEL);
+       retval = flex_array_prealloc(group, 0, group_size, GFP_KERNEL);
        if (retval)
                goto out_free_group_list;