tag f250dc9bf9d40356ebf3abe5dac6776d5f8fc10c
tagger The Android Open Source Project <initial-contribution@android.com> Mon Jan 04 13:48:21 2016 -0800
object 84ad5a41163aefefc6db772c5e51f93deefa533a

Android 5.1.1 Release 0.24

commit 84ad5a41163aefefc6db772c5e51f93deefa533a
author Mark Salyzyn <salyzyn@google.com> Fri Nov 13 13:18:22 2015 -0800
committer Mark Salyzyn <salyzyn@google.com> Fri Nov 13 13:18:26 2015 -0800
tree 2ee1f02690cef36788d1e8fafc0a4fbd9e20655d
parent 0ee50d53a5f85c9f587b0926bd5d7884d90c21dc

manta_defconfig: remove SYSVIPC

System V IPCs are not compliant with Android's application lifecycle
because allocated resources are not freeable by the low memory killer.
This lead to global kernel resource leakage.

For example, there is no way to automatically release a SysV
semaphore allocated in the kernel when:
- a buggy or malicious process exits
- a non-buggy and non-malicious process crashes or is explicitly
  killed.

Killing processes automatically to make room for new ones is an
important part of Android's application lifecycle implementation.
This means that, even assuming only non-buggy and non-malicious
code, it is very likely that over time, the kernel global tables
used to implement SysV IPCs will fill up.

Signed-off-by: Jeff Vander Stoep <jeffv@google.com>
Signed-off-by: Mark Salyzyn <salyzyn@google.com>
Bug: 22300191
Change-Id: Icecf2743dcf6ae12b7a8539a52ead3576b82f748