From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753766AbbAMT2v (ORCPT ); Tue, 13 Jan 2015 14:28:51 -0500 Received: from casper.infradead.org ([85.118.1.10]:54216 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751413AbbAMT2u (ORCPT ); Tue, 13 Jan 2015 14:28:50 -0500 Date: Tue, 13 Jan 2015 19:28:47 +0000 From: Thomas Graf To: Cong Wang Cc: Ying Xue , "linux-kernel@vger.kernel.org" , lkp@01.org, Netdev Subject: Re: Fwd: [rhashtable] WARNING: CPU: 0 PID: 10 at kernel/locking/mutex.c:570 mutex_lock_nested() Message-ID: <20150113192847.GP20387@casper.infradead.org> References: <20150110194803.GA9033@wfg-t540p.sh.intel.com> <54B3259B.7080601@windriver.com> <20150112124216.GA26570@casper.infradead.org> <54B4CE3E.8020009@windriver.com> <20150113084126.GE20387@casper.infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-SRS-Rewrite: SMTP reverse-path rewritten from by casper.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/13/15 at 11:14am, Cong Wang wrote: > On Tue, Jan 13, 2015 at 12:41 AM, Thomas Graf wrote: > > I can't reproduce it in my KVM box either so far. It looks like a > > mutex_lock() on an uninitialized mutex or use after free but I can't > > find such a code path so far. > > Couldn't that be the delayed work is still running after rhashtable > is destroyed by its caller? I mean, cancel_delayed_work_sync() > should be called in rhashtable_destroy()? > > Of course, it may be caller's responsibility to ensure that, I haven't > looked into it that much. Yes, we came to the very same conclusion in a different email thread and found the offending race condition.