linux-kernel - Re: [PATCH] ARM: EXYNOS: Handle of_find_device_by

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] [day] [month] [year] [list]

Date:	Wed, 18 Mar 2015 18:30:34 +0100
From:	Krzysztof Kozlowski <k.kozlowski@...sung.com>
To:	Kukjin Kim <kgene@...nel.org>
Cc:	linux-arm-kernel@...ts.infradead.org,
	Krzysztof Kozlowski <k.kozlowski@...sung.com>,
	linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
	Kyungmin Park <kyungmin.park@...sung.com>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
	Marek Szyprowski <m.szyprowski@...sung.com>
Subject: Re: [PATCH] ARM: EXYNOS: Handle of_find_device_by_node and kstrdup failures

2015-02-24 16:42 GMT+01:00 Krzysztof Kozlowski <k.kozlowski@...sung.com>:
> On wto, 2015-02-03 at 18:28 +0100, Krzysztof Kozlowski wrote:
>> Prevent possible NULL pointer dereference of pointer returned by
>> of_find_device_by_node(). Handle this by skipping such power domain.
>>
>> Additionally fail the init on kstrdup() failure. Such case is actually
>> not fatal because the name for power domain allocated by kstrdup() is
>> used only in printk. Still as a precaution handle this as an error
>> condition.
>>
>> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@...sung.com>
>
> Hi Kukjin,
>
> What is the status of this patch and the "ARM: EXYNOS: Handle of
> of_iomap() failure". The latter should be in your tree but I cannot find
> it.
>
> Best regards,
> Krzysztof

Hi Kukjin,

You haven't applied this and the "ARM: EXYNOS: Handle of of_iomap()
failure" yet. Any comments?

Best regards,
Krzysztof
--
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/