From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754980AbaDGINr (ORCPT ); Mon, 7 Apr 2014 04:13:47 -0400 Received: from merlin.infradead.org ([205.233.59.134]:39432 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753317AbaDGINn (ORCPT ); Mon, 7 Apr 2014 04:13:43 -0400 Date: Mon, 7 Apr 2014 10:13:36 +0200 From: Peter Zijlstra To: Vladimir Davydov Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, devel@openvz.org, Ingo Molnar Subject: Re: [PATCH -mm 2/3] lockdep: mark rwsem_acquire_read as recursive Message-ID: <20140407081336.GC11096@twins.programming.kicks-ass.net> References: <8c6473e959a4557d8622a6d7ff24888cb3f7512d.1396779337.git.vdavydov@parallels.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8c6473e959a4557d8622a6d7ff24888cb3f7512d.1396779337.git.vdavydov@parallels.com> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Apr 06, 2014 at 07:33:51PM +0400, Vladimir Davydov wrote: > rw_semaphore implementation allows recursing calls to down_read, but > lockdep thinks that it doesn't. As a result, it will complain > false-positively, e.g. if we do not observe some predefined locking > order when taking an rw semaphore for reading and a mutex. > > This patch makes lockdep think rw semaphore is read-recursive, just like > rw spin lock. Uhm no rwsem isn't read recursive. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ig0-f175.google.com (mail-ig0-f175.google.com [209.85.213.175]) by kanga.kvack.org (Postfix) with ESMTP id 4E7CA6B0031 for ; Mon, 7 Apr 2014 04:13:42 -0400 (EDT) Received: by mail-ig0-f175.google.com with SMTP id ur14so3312676igb.14 for ; Mon, 07 Apr 2014 01:13:42 -0700 (PDT) Received: from merlin.infradead.org (merlin.infradead.org. [2001:4978:20e::2]) by mx.google.com with ESMTPS id p6si17746796icc.57.2014.04.07.01.13.41 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 07 Apr 2014 01:13:41 -0700 (PDT) Date: Mon, 7 Apr 2014 10:13:36 +0200 From: Peter Zijlstra Subject: Re: [PATCH -mm 2/3] lockdep: mark rwsem_acquire_read as recursive Message-ID: <20140407081336.GC11096@twins.programming.kicks-ass.net> References: <8c6473e959a4557d8622a6d7ff24888cb3f7512d.1396779337.git.vdavydov@parallels.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8c6473e959a4557d8622a6d7ff24888cb3f7512d.1396779337.git.vdavydov@parallels.com> Sender: owner-linux-mm@kvack.org List-ID: To: Vladimir Davydov Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, devel@openvz.org, Ingo Molnar On Sun, Apr 06, 2014 at 07:33:51PM +0400, Vladimir Davydov wrote: > rw_semaphore implementation allows recursing calls to down_read, but > lockdep thinks that it doesn't. As a result, it will complain > false-positively, e.g. if we do not observe some predefined locking > order when taking an rw semaphore for reading and a mutex. > > This patch makes lockdep think rw semaphore is read-recursive, just like > rw spin lock. Uhm no rwsem isn't read recursive. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org