From mboxrd@z Thu Jan 1 00:00:00 1970 From: sboyd@codeaurora.org (Stephen Boyd) Date: Tue, 29 Oct 2013 13:51:31 -0700 Subject: [PATCH 1/6] edac: Don't try to cancel workqueue when it's never setup In-Reply-To: <20131029204827.GM10972@pd.tnic> References: <1383006690-6754-1-git-send-email-sboyd@codeaurora.org> <1383006690-6754-2-git-send-email-sboyd@codeaurora.org> <20131029204827.GM10972@pd.tnic> Message-ID: <52701FD3.8040407@codeaurora.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 10/29/13 13:48, Borislav Petkov wrote: > On Mon, Oct 28, 2013 at 05:31:25PM -0700, Stephen Boyd wrote: >> We only setup a workqueue for edac devices that use the polling >> method. We still try to cancel the workqueue if an edac_device >> uses the irq method though. This causes a warning from debug >> objects when we remove an edac device: >> >> WARNING: CPU: 0 PID: 56 at lib/debugobjects.c:260 debug_print_object+0x98/0xc0() >> ODEBUG: assert_init not available (active state 0) object type: timer_list hint: stub_timer+0x0/0x28 >> Modules linked in: krait_edac(-) >> CPU: 0 PID: 56 Comm: rmmod Not tainted 3.12.0-rc2-00035-g15292a0 #69 >> [] (unwind_backtrace+0x0/0x144) from [] (show_stack+0x20/0x24) >> [] (show_stack+0x20/0x24) from [] (dump_stack+0x74/0xb4) >> [] (dump_stack+0x74/0xb4) from [] (warn_slowpath_common+0x78/0x9c) >> [] (warn_slowpath_common+0x78/0x9c) from [] (warn_slowpath_fmt+0x40/0x48) >> [] (warn_slowpath_fmt+0x40/0x48) from [] (debug_print_object+0x98/0xc0) >> [] (debug_print_object+0x98/0xc0) from [] (debug_object_assert_init+0xdc/0xec) >> [] (debug_object_assert_init+0xdc/0xec) from [] (del_timer+0x24/0x7c) >> [] (del_timer+0x24/0x7c) from [] (try_to_grab_pending+0xc0/0x1b0) >> [] (try_to_grab_pending+0xc0/0x1b0) from [] (cancel_delayed_work+0x2c/0xa0) >> [] (cancel_delayed_work+0x2c/0xa0) from [] (edac_device_workq_teardown+0x1c/0x38) >> [] (edac_device_workq_teardown+0x1c/0x38) from [] (edac_device_del_device+0xb8/0xe4) >> [] (edac_device_del_device+0xb8/0xe4) from [] (krait_edac_remove+0x50/0x70 [krait_edac]) >> [] (krait_edac_remove+0x50/0x70 [krait_edac]) from [] (platform_drv_remove+0x24/0x28) >> [] (platform_drv_remove+0x24/0x28) from [] (__device_release_driver+0x68/0xc0) >> [] (__device_release_driver+0x68/0xc0) from [] (driver_detach+0xc4/0xc8) >> [] (driver_detach+0xc4/0xc8) from [] (bus_remove_driver+0xac/0x114) >> [] (bus_remove_driver+0xac/0x114) from [] (driver_unregister+0x38/0x58) >> [] (driver_unregister+0x38/0x58) from [] (platform_driver_unregister+0x1c/0x20) >> [] (platform_driver_unregister+0x1c/0x20) from [] (krait_edac_driver_exit+0x14/0x1c [krait_edac]) >> [] (krait_edac_driver_exit+0x14/0x1c [krait_edac]) from [] (SyS_delete_module+0x178/0x2b4) >> [] (SyS_delete_module+0x178/0x2b4) from [] (ret_fast_syscall+0x0/0x48) >> >> Fix it by skipping the workqueue teardown for such devices. >> >> Signed-off-by: Stephen Boyd > Acked-by: Borislav Petkov > > Btw, you might want to remove the hex numbers in the trace above and > leave only the call stack to make it more readable. > Thanks. I'll do that in the next round. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation