shm_try_destroy_orphaned() and shm_try_destroy_current() didn't handle
the case of separate PID namespaces, but a single IPC namespace.  If
there are tasks with the same PID values using the same shmem object,
the wrong destroy decision could be reached.

On shm segment creation store the pointer to the creator task in
shmid_kernel->shm_creator field and zero it on task exit.  Then
use the ->shm_creator insread of shm_cprid in both functions.  As
shmid_kernel object is already locked at this stage, no additional
locking is needed.
Signed-off-by: NVasiliy Kulikov <segoon@openwall.com>
Acked-by: NSerge Hallyn <serge.hallyn@canonical.com>
Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>