diff options
| author | Olav Haugan <ohaugan@codeaurora.org> | 2013-11-04 15:51:51 -0800 |
|---|---|---|
| committer | Simon Shields <keepcalm444@gmail.com> | 2016-06-12 21:19:49 +1000 |
| commit | 2ee074b5fc854501be8d25fe4cae23402e5d1812 (patch) | |
| tree | 5495efd8f3886350a9dd56e76c5ae1c5c6f81f03 /drivers/interceptor | |
| parent | 195db76c72c596469fc6a194f968ccec33f1de09 (diff) | |
| download | kernel_samsung_smdk4412-2ee074b5fc854501be8d25fe4cae23402e5d1812.tar.gz kernel_samsung_smdk4412-2ee074b5fc854501be8d25fe4cae23402e5d1812.tar.bz2 kernel_samsung_smdk4412-2ee074b5fc854501be8d25fe4cae23402e5d1812.zip | |
staging: zsmalloc: Ensure handle is never 0 on success
zsmalloc encodes a handle using the pfn and an object
index. On hardware platforms with physical memory starting
at 0x0 the pfn can be 0. This causes the encoded handle to be
0 and is incorrectly interpreted as an allocation failure.
This issue affects all current and future SoCs with physical
memory starting at 0x0. All MSM8974 SoCs which includes
Google Nexus 5 devices are affected.
To prevent this false error we ensure that the encoded handle
will not be 0 when allocation succeeds.
Change-Id: I5ad31712be4dd5105ebee81fa95927039c0f6935
Signed-off-by: Olav Haugan <ohaugan@codeaurora.org>
Diffstat (limited to 'drivers/interceptor')
0 files changed, 0 insertions, 0 deletions