diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2015-09-30 12:48:40 -0400 |
|---|---|---|
| committer | Ben Hutchings <ben@decadent.org.uk> | 2015-10-13 03:46:12 +0100 |
| commit | 2ef259c0f5b2f3ca28ccb7bf126a0a2177012f89 (patch) | |
| tree | 8a5b7f4e97d14301cd67fb10894a8954f75fb9c5 /lib | |
| parent | 0bdf1e820160cdeb16cba1c5ea6892ae982a6587 (diff) | |
| download | kernel_samsung_smdk4412-2ef259c0f5b2f3ca28ccb7bf126a0a2177012f89.zip kernel_samsung_smdk4412-2ef259c0f5b2f3ca28ccb7bf126a0a2177012f89.tar.gz kernel_samsung_smdk4412-2ef259c0f5b2f3ca28ccb7bf126a0a2177012f89.tar.bz2 | |
Initialize msg/shm IPC objects before doing ipc_addid()
commit b9a532277938798b53178d5a66af6e2915cb27cf upstream.
As reported by Dmitry Vyukov, we really shouldn't do ipc_addid() before
having initialized the IPC object state. Yes, we initialize the IPC
object in a locked state, but with all the lockless RCU lookup work,
that IPC object lock no longer means that the state cannot be seen.
We already did this for the IPC semaphore code (see commit e8577d1f0329:
"ipc/sem.c: fully initialize sem_array before making it visible") but we
clearly forgot about msg and shm.
Reported-by: Dmitry Vyukov <dvyukov@google.com>
Cc: Manfred Spraul <manfred@colorfullife.com>
Cc: Davidlohr Bueso <dbueso@suse.de>
Cc: stable@vger.kernel.org
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
[bwh: Backported to 3.2:
- Adjust context
- The error path being moved looks a little different]
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Diffstat (limited to 'lib')
0 files changed, 0 insertions, 0 deletions