linux-kernel - Re: [PATCH] CMA: Don't return a valid cma for non-cma dev

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 31 Jul 2015 19:46:30 +0200
From:	Michal Nazarewicz <mina86@...a86.com>
To:	Feng Tang <feng.tang@...el.com>
Cc:	"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
	"m.szyprowski\@samsung.com" <m.szyprowski@...sung.com>,
	"kyungmin.park\@samsung.com" <kyungmin.park@...sung.com>,
	"akpm\@linux-foundation.org" <akpm@...ux-foundation.org>,
	"iamjoonsoo.kim\@lge.com" <iamjoonsoo.kim@....com>
Subject: Re: [PATCH] CMA: Don't return a valid cma for non-cma dev

On Fri, Jul 31 2015, Feng Tang wrote:
> Maybe I didn't make my problem clear, for our platform, we do need to
> use cma as we have camera ISP which has no IOMMU, so we cannot set
> "cma=0".

Then specify a CMA region for the camera in platform initialisation code
or device trees or whatever else is the rave nowadays.

I’m assuming that you have a piece of code (or configuration of some
sort) that assigns a CMA region to the device (otherwise ‘dev->cma_area’
would be NULL and your patch would just always get you NULL CMA area).
Simply create a CMA area there and assign it to the device.

-- 
Best regards,                                         _     _
.o. | Liege of Serenely Enlightened Majesty of      o' \,=./ `o
..o | Computer Science,  Michał “mina86” Nazarewicz    (o o)
ooo +--<mpn@...gle.com>--<xmpp:mina86@...ber.org>--ooO--(_)--Ooo--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/