Re: [PATCH] soc: imx: imx-scu: Getting UID from SCU should have response

On Wed, Sep 04, 2019 at 03:13:14PM -0400, Anson Huang wrote: > The SCU firmware API for getting UID should have response, > otherwise, the message stored in function stack could be > released and then the response data received from SCU will be > stored into that released stack and cause kernel NUL

RE: [PATCH] soc: imx: imx-scu: Getting UID from SCU should have response

Hi, Leonard > On 2019-09-04 10:14 AM, Anson Huang wrote: > > The SCU firmware API for getting UID should have response, otherwise, > > the message stored in function stack could be released and then the > > response data received from SCU will be stored into that released > > stack and cause kerne

Re: [PATCH] soc: imx: imx-scu: Getting UID from SCU should have response

On 2019-09-04 10:14 AM, Anson Huang wrote: > The SCU firmware API for getting UID should have response, > otherwise, the message stored in function stack could be > released and then the response data received from SCU will be > stored into that released stack and cause kernel NULL pointer > dump.

[PATCH] soc: imx: imx-scu: Getting UID from SCU should have response

The SCU firmware API for getting UID should have response, otherwise, the message stored in function stack could be released and then the response data received from SCU will be stored into that released stack and cause kernel NULL pointer dump. Fixes: 73feb4d0f8f1 ("soc: imx-scu: Add SoC UID(uniq