[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20181212022506.171936-1-dbasehore@chromium.org>
Date: Tue, 11 Dec 2018 18:25:05 -0800
From: Derek Basehore <dbasehore@...omium.org>
To: peterz@...radead.org
Cc: mingo@...hat.com, will.deacon@....com,
linux-kernel@...r.kernel.org,
Derek Basehore <dbasehore@...omium.org>
Subject: RFC [PATCH 0/1] Fix lockdep false positive
I'm not sure if I'm breaking any detection with this patch since I
haven't looked at that lockdep code before. I do know that the unlock
order for locks with a nest lock should not matter, though.
Specifically, you should be able to unlock the nest lock followed by
all the locks nested underneath it.
Derek Basehore (1):
locking/lockdep: Fix nest lock warning on unlock
kernel/locking/lockdep.c | 27 +++++++++++++--------------
1 file changed, 13 insertions(+), 14 deletions(-)
--
2.20.0.rc2.403.gdbc3b29805-goog
Powered by blists - more mailing lists