Re: [PATCH] iommu/exynos: Remove initconst attribute to avoid potential kernel oops

2017-10-11 Thread Joerg Roedel
On Wed, Oct 11, 2017 at 07:49:05AM +0200, Marek Szyprowski wrote: > Could you also apply it to v4.14-fixes, or is it too late for that? Well, I already pushed it out, but I guess I can still move the patch to another branch. Joerg ___ iommu

Re: [PATCH] iommu/exynos: Remove initconst attribute to avoid potential kernel oops

2017-10-10 Thread Marek Szyprowski
Hi Joerg, On 2017-10-10 14:13, Joerg Roedel wrote: On Mon, Oct 09, 2017 at 01:40:23PM +0200, Marek Szyprowski wrote: Exynos SYSMMU registers standard platform device with sysmmu_of_match table, what means that this table is accessed every time a new platform device is registered in a system.

Re: [PATCH] iommu/exynos: Remove initconst attribute to avoid potential kernel oops

2017-10-10 Thread Joerg Roedel
On Mon, Oct 09, 2017 at 01:40:23PM +0200, Marek Szyprowski wrote: > Exynos SYSMMU registers standard platform device with sysmmu_of_match > table, what means that this table is accessed every time a new platform > device is registered in a system. This might happen also after the boot, > so the

Re: [PATCH] iommu/exynos: Remove initconst attribute to avoid potential kernel oops

2017-10-09 Thread Krzysztof Kozlowski
On Mon, Oct 9, 2017 at 1:40 PM, Marek Szyprowski wrote: > Exynos SYSMMU registers standard platform device with sysmmu_of_match > table, what means that this table is accessed every time a new platform > device is registered in a system. This might happen also after the

[PATCH] iommu/exynos: Remove initconst attribute to avoid potential kernel oops

2017-10-09 Thread Marek Szyprowski
Exynos SYSMMU registers standard platform device with sysmmu_of_match table, what means that this table is accessed every time a new platform device is registered in a system. This might happen also after the boot, so the table must not be attributed as initconst to avoid potential kernel oops