| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <1304715928-19266-2-git-send-email-andi@firstfloor.org> Date: Fri, 6 May 2011 14:05:25 -0700 From: Andi Kleen <andi@...stfloor.org> To: linux-kernel@...r.kernel.org Cc: peterz@...radead.org, arnd@...db.de, akpm@...ux-foundation.org, Andi Kleen <ak@...ux.intel.com> Subject: [PATCH 1/4] BKL: Remove BKL references in mutex code From: Andi Kleen <ak@...ux.intel.com> The mutex code still checks for the BKL which is already gone. Remove that code. Signed-off-by: Andi Kleen <ak@...ux.intel.com> --- kernel/mutex.c | 7 ------- 1 files changed, 0 insertions(+), 7 deletions(-) diff --git a/kernel/mutex.c b/kernel/mutex.c index c4195fa..62d0a06 100644 --- a/kernel/mutex.c +++ b/kernel/mutex.c @@ -163,13 +163,6 @@ __mutex_lock_common(struct mutex *lock, long state, unsigned int subclass, struct thread_info *owner; /* - * If we own the BKL, then don't spin. The owner of - * the mutex might be waiting on us to release the BKL. - */ - if (unlikely(current->lock_depth >= 0)) - break; - - /* * If there's an owner, wait for it to either * release the lock or go to sleep. */ -- 1.7.4.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists