That depends on where else you need these variables.
> The root of the problem is that the reference count is being relied on
> for the wrong thing. There is a race on p->user between the
> dup_task_struct() and whenever the atomic_inc(&p->user->__count)
> occcurs. The user reference count needs to be incremented in
> dup_task_struct(), before the copy occurs.
I don't get you. The user_struct can hardly go away while we are
IMHO you should add a spinlock to user_struct and take it.
A clear solution that doesn't hurt the common case.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/