From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751195AbdFBIvy (ORCPT ); Fri, 2 Jun 2017 04:51:54 -0400 Received: from s3.sipsolutions.net ([5.9.151.49]:40128 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751161AbdFBIvv (ORCPT ); Fri, 2 Jun 2017 04:51:51 -0400 Message-ID: <1496393508.20223.0.camel@sipsolutions.net> Subject: Re: single-threaded wq lockdep is broken From: Johannes Berg To: Lai Jiangshan Cc: Tejun Heo , linux-kernel Date: Fri, 02 Jun 2017 10:51:48 +0200 In-Reply-To: (sfid-20170602_090400_729536_8FF35C48) References: <1495999993.3578.1.camel@sipsolutions.net> <1496219796.18378.1.camel@sipsolutions.net> (sfid-20170602_090400_729536_8FF35C48) Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2017-06-02 at 15:03 +0800, Lai Jiangshan wrote: > > the @w2 is not queued before flush_work(&w2), it is expected > that @w2 is not associated with @wq, and the dependence > mtx -> wq will not be recorded. And it is expected no warning. Lockdep is symmetric. So then maybe it won't warn when executing flush_work(), but should later when executing @w2. No real difference? johannes