mm-video: vidc: removed the async v4l2 event for session unsupported

When driver detects the session unsupported error, it will return error
and a async v4l2 event to OMX component. OMX component will report
error to client once receiving this returned error. Client is going
to destroy the OMX component. If the v4l2 event reaches at client
when client already destroy the OMX component. Assert failure will
happen.

CRs-fixed: 702914
Change-Id: Iede16ebf5b5f0216b18de71b8d3cbe669597188a
Signed-off-by: Jia Meng <jmeng@codeaurora.org>
Merge "mm-video: vidc: removed the async v4l2 event for session unsupported"
ASoC: wcd9306: fix the NULL pointer dereference in the tapan codec

During the close of the AFE port the AIF1 PB widget will be closed
which access the core variable.
If the core is not initialized yet it will result in the kernel panic.
Fix by adding the check for the core structure to be initialized.

CRs-Fixed: 635790
Change-Id: Ic057e2eb75b25dbc55aa06cbce2b49aca0b1b25f
Signed-off-by: Aviral Gupta <aviralg@codeaurora.org>
Merge "ASoC: wcd9306: fix the NULL pointer dereference in the tapan codec"
ASoC: msm: Fix ADM GET PARAM callback

Add size check on inband get param call and do
not process inband if RTAC is active.

Change-Id: I2c099f5ea254a214f224dda556773a7fe6754fe5
CRs-fixed: 548397
Signed-off-by: Ben Romberger <bromberg@codeaurora.org>
Merge "ASoC: msm: Fix ADM GET PARAM callback"
crypto: msm: check potential integer overflow

According to the specification of AEAD, AEAD request crypt length is
not a fixed maximum and associated length is also same. This could
lead to potential integer overflow, thus allocating less memory. So
we need to check potential integer overflow on AEAD request length.

CRs-Fixed: 726872
Change-Id: Ie7708000bfd8c57e2fba8e02230a7ce9cdc9634c
Signed-off-by: William Clark <wclark@codeaurora.org>
Merge "crypto: msm: check potential integer overflow"