summaryrefslogtreecommitdiffstats
path: root/drivers/staging/tidspbridge
diff options
context:
space:
mode:
authorOlav Haugan <ohaugan@codeaurora.org>2013-11-22 09:30:41 -0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2013-11-25 12:52:45 -0800
commit67296874eb1cc80317bf2a8fba22b494e21eb29b (patch)
treebed05c365a16261e247c387dfa26a1e47bf6bfed /drivers/staging/tidspbridge
parentb39f15c972c462903208531b82f9b34ba8ef3ec0 (diff)
downloadop-kernel-dev-67296874eb1cc80317bf2a8fba22b494e21eb29b.zip
op-kernel-dev-67296874eb1cc80317bf2a8fba22b494e21eb29b.tar.gz
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. Signed-off-by: Olav Haugan <ohaugan@codeaurora.org> Cc: stable <stable@vger.kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/staging/tidspbridge')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud