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
| ||
|
Date: Tue, 27 Nov 2012 13:31:15 +0200 From: Terje Bergström <tbergstrom@...dia.com> To: Thierry Reding <thierry.reding@...onic-design.de> CC: Lucas Stach <dev@...xeye.de>, Dave Airlie <airlied@...il.com>, "linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>, "dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Arto Merilainen <amerilainen@...dia.com> Subject: Re: [RFC v2 8/8] drm: tegra: Add gr2d device On 27.11.2012 12:37, Thierry Reding wrote: > But in that case it should be made mandatory at first until proper IOMMU > support is enabled on Tegra30. Then it can be checked at driver probe > time whether or not to enable the extra checks. That way we don't need a > special Kconfig option and we still get all the security that we need, > right? I guess it depends on the level of security. If we want to only protect kernel and user space memory, this would be sufficient and no firewall is needed if IOMMU is turned on. If we want to protect 2D buffers from each other, this is not sufficient. Terje -- 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/
Powered by blists - more mailing lists