mirror of
git://nv-tegra.nvidia.com/linux-nv-oot.git
synced 2025-12-24 02:01:36 +03:00
When CONFIG_V4L2_ASYNC is not enabled and CONFIG_DEBUG_LIST is enabled then the following kernel panic is observed ... imx219: probe of 9-0010 failed with error -524 list_add corruption. next->prev should be prev (ffffb2b2e95dad78), but was 0000000000000000. (next=ffff000088baf508). ------------[ cut here ]------------ kernel BUG at lib/list_debug.c:23! Internal error: Oops - BUG: 00000000f2000800 [#1] SMP If CONFIG_V4L2_ASYNC is not enabled in the kernel, then the function tegracam_v4l2subdev_register() will return -ENOTSUPP and this will cause the probe of the sensor drivers to fail. Although failing to probe the driver is expected in this case, it is not expected that this will trigger a kernel panic if CONFIG_DEBUG_LIST is enabled. The panic is caused because tegracam_device_unregister() is not being called in the exit path of the probe function when tegracam_v4l2subdev_register() returns an error. Bug 4704110 Change-Id: I4875a31e55c24b5ab0932a683f16a7a74695a6b6 Signed-off-by: Jon Hunter <jonathanh@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/c/linux-nv-oot/+/3162389 Reviewed-by: Paritosh Dixit <paritoshd@nvidia.com> GVS: buildbot_gerritrpt <buildbot_gerritrpt@nvidia.com> Reviewed-by: Ankur Pawar <ankurp@nvidia.com>
20 KiB
20 KiB