From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753192AbdI1Ntw (ORCPT ); Thu, 28 Sep 2017 09:49:52 -0400 Received: from mail-pg0-f48.google.com ([74.125.83.48]:56384 "EHLO mail-pg0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752983AbdI1Ntu (ORCPT ); Thu, 28 Sep 2017 09:49:50 -0400 X-Google-Smtp-Source: AOwi7QAhNp47p6EWjsHPGQG6DKo8IVQA+pd/xZFUyUbI5DXdX+5pb0Tmr9FtmBIeplaRLKFGnmXWjA== Date: Thu, 28 Sep 2017 21:50:29 +0800 From: Boqun Feng To: Byungchul Park Cc: linux-kernel@vger.kernel.org, "Paul E. McKenney" , Steven Rostedt , Peter Zijlstra , Ingo Molnar , kernel-team@lge.com Subject: Re: [PATCH] lockdep: Print proper scenario if cross deadlock detected at acquisition time Message-ID: <20170928135029.c3wnllu43h7f3xmn@tardis> References: <20170919125218.17802-1-boqun.feng@gmail.com> <20170927013145.GR5994@X58A-UD3R> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="nnzn3is35tujl65q" Content-Disposition: inline In-Reply-To: <20170927013145.GR5994@X58A-UD3R> User-Agent: NeoMutt/20170912 (1.9.0) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --nnzn3is35tujl65q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 27, 2017 at 01:31:45AM +0000, Byungchul Park wrote: >=20 > Sometimes, it gives a wrong scenario. For example: >=20 > lock target > lock source > lock parent > lock target > lock parent of parent > lock parent >=20 > lock parent of parent > unlock source >=20 > We should consider this scenario as well so the report is always true > generally. >=20 Right, let me think about a proper way to do this. Regards, Boqun > > + printk(KERN_CONT ");\n"); > > + printk("\n *** DEADLOCK ***\n\n"); > > } else { > > printk(" Possible unsafe locking scenario:\n\n"); > > printk(" CPU0 CPU1\n"); > > --=20 > > 2.14.1 --nnzn3is35tujl65q Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEj5IosQTPz8XU1wRHSXnow7UH+rgFAlnM/iEACgkQSXnow7UH +rit7wf9HQ9IWDBRrbmfUgYZu8AMt6vanyTvI9DuPB1JqHRvx7VIWXgzR4L8Ajl2 Jh8N78ZFyXIvlzFoXnitjtx0udPaoAtHTMfL10QY9LWViW8eBGPO5WG+SsysxloG Pv8sGQzgjOHqjdOl0GUbV7JlxKs4DDdhPRNlJIOAwmj8ocy1d4r6TcTaMA5j8SzJ MFEDLA9bqnU7knqz4H69ia8MHqaBF6e0rMx90BkUAqYZAQZLYSIVJN6qI/PU5rSF O/nzGAcz2xHYNYKEk0B8i0n9WB6LjsGNjKXglzWAWjitXEGfR2JOkk0XT715X9FQ s8q97jzxLbRAxANDUQq1rijISm8kAA== =sW53 -----END PGP SIGNATURE----- --nnzn3is35tujl65q--