Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752515Ab3J2Usg (ORCPT ); Tue, 29 Oct 2013 16:48:36 -0400 Received: from mail.skyhub.de ([78.46.96.112]:37772 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751615Ab3J2Use (ORCPT ); Tue, 29 Oct 2013 16:48:34 -0400 Date: Tue, 29 Oct 2013 21:48:27 +0100 From: Borislav Petkov To: Stephen Boyd Cc: linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 1/6] edac: Don't try to cancel workqueue when it's never setup Message-ID: <20131029204827.GM10972@pd.tnic> References: <1383006690-6754-1-git-send-email-sboyd@codeaurora.org> <1383006690-6754-2-git-send-email-sboyd@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1383006690-6754-2-git-send-email-sboyd@codeaurora.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3272 Lines: 52 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. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/