On Sat, 20 Jan 2018, Greg KH wrote:
> On Fri, Jan 19, 2018 at 11:16:47AM -0800, Liam Mark wrote:
> > Since the CMA API is now used directly the allocated memory is no longer
> > automatically zeroed.
> >
> > Explicitly zero CMA allocated memory to ensure that no data is exposed
> > to userspace.
On Fri, 19 Jan 2018, Dan Carpenter wrote:
> On Fri, Jan 19, 2018 at 11:16:47AM -0800, Liam Mark wrote:
> > Since the CMA API is now used directly the allocated memory is no longer
> > automatically zeroed.
> >
> > Explicitly zero CMA allocated memory to ensure that no data is exposed
> > to users
On Fri, Jan 19, 2018 at 11:16:47AM -0800, Liam Mark wrote:
> Since the CMA API is now used directly the allocated memory is no longer
> automatically zeroed.
>
> Explicitly zero CMA allocated memory to ensure that no data is exposed
> to userspace.
How far back does this patch need to be ported?
On Fri, Jan 19, 2018 at 11:16:47AM -0800, Liam Mark wrote:
> Since the CMA API is now used directly the allocated memory is no longer
> automatically zeroed.
>
> Explicitly zero CMA allocated memory to ensure that no data is exposed
> to userspace.
>
> Change-Id: I08e143707a0d31610821a7f16826c262