[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200327044830.qw74dvaxkjg75fh5@linux-p48b>
Date: Thu, 26 Mar 2020 21:48:30 -0700
From: Davidlohr Bueso <dave@...olabs.net>
To: Michel Lespinasse <walken@...gle.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-mm <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Laurent Dufour <ldufour@...ux.ibm.com>,
Vlastimil Babka <vbabka@...e.cz>,
Matthew Wilcox <willy@...radead.org>,
Liam Howlett <Liam.Howlett@...cle.com>,
Jerome Glisse <jglisse@...hat.com>,
David Rientjes <rientjes@...gle.com>,
Hugh Dickins <hughd@...gle.com>, Ying Han <yinghan@...gle.com>,
Jason Gunthorpe <jgg@...pe.ca>,
Markus Elfring <Markus.Elfring@....de>
Subject: Re: [PATCH v2 09/10] mmap locking API: use lockdep_assert_held
On Thu, 26 Mar 2020, Michel Lespinasse wrote:
>Use lockdep_assert_held when asserting that mmap_sem is held.
>
>Using this instead of rwsem_is_locked makes the assertions more
>tolerant of future changes to the lock type.
Not opposing here, just worth mentioning that the coverage surface
is greatly reduced, lockdep not being very popular in production.
Thanks,
Davidlohr
Powered by blists - more mailing lists