Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp317148yba; Thu, 16 May 2019 01:01:55 -0700 (PDT) X-Google-Smtp-Source: APXvYqybCTxLELwFRfhLAnuYuU7fpQ6deNMcySDWhoQK+hC2UhKjzLqnnPci6Y4zHxz4rm+0mL/k X-Received: by 2002:a62:585:: with SMTP id 127mr32592873pff.231.1557993715453; Thu, 16 May 2019 01:01:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557993715; cv=none; d=google.com; s=arc-20160816; b=jYtXnE02RSggZBWJjGvzkN31cKbIK0AaKsz2lVH8pqWjo3yTjifigWg3umDazkXeuJ i+ZjZE0ajCgge8h+1ewnDxivNzBREoevCXUC+JQTVWuiX+77Noc9s++wqnFk0uxJzWYH MlANzk8KEPqGN6hTpHaDyZGJJpqxN49xGpPv1D+S9voN0LneKHWrI7IMqhlNxMVau0n8 4e99qG9skq125ZzyloO7GnDhA3ArkMH/58uhhY721b9gVFsJw0uBEuR8IvLYQLYtKFNb qtRXv11L2EOdYiLauCdrYwPc86bZe/tCPVO1kolwfr5CFyHFsfhQ4p4W4N+NSpqReiML iMcQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=PMKaB0Oa5QXUNtHyl3wAgOjSQCtL7tLwsVttCyl931A=; b=nzDmnqHW+21dNdCfdL5S+gBir3eL5tytmQb4FwhdoyjPt8Yos6Evz8dkot2zk88Ksp vvPE3cdh6XVG5IwgYRjIomUphOwsSiA1XJyd/dwtgiEdPzp56hfujRgeVSF/qIIw87TZ scq9UWqIJdYV/PyGBxTBH/nLVwo+faI7Z2aWItCqMcquxu2OlENg85Sch7oHku81VMum 8kCmCKJRIJCngWDmbY7txkbsV5T1Xasgu0PraInCEfs/MUC4A1L4LqBHJMeE1q0+cV1e NBYNSL7lcdsbq5o9CcYCgcLidRSRoRUmZ6YiUaiLXzK1NYodlplLunWIsJ1mz5S5d655 hUiw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=mNebwHl3; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g3si5166034pfq.30.2019.05.16.01.01.39; Thu, 16 May 2019 01:01:55 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=mNebwHl3; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726772AbfEPIA2 (ORCPT + 99 others); Thu, 16 May 2019 04:00:28 -0400 Received: from mail-pf1-f194.google.com ([209.85.210.194]:34076 "EHLO mail-pf1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726363AbfEPIA1 (ORCPT ); Thu, 16 May 2019 04:00:27 -0400 Received: by mail-pf1-f194.google.com with SMTP id n19so1432185pfa.1 for ; Thu, 16 May 2019 01:00:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=PMKaB0Oa5QXUNtHyl3wAgOjSQCtL7tLwsVttCyl931A=; b=mNebwHl3556stsQHTW1xYb9i00Zjjy5fbFM+qBbXUliEAsVVZNhEhp43EmfV5B2vRU boj13OY5+UPXztGPhm7/ShGDQUa31xDy82gKWtqqMW9WKiGJPSQWKCRMBacgeePPiX0D 7Luyvc89GKpZSSl6avKi3kSoSqjM+PWsu3bp2nNnWjcBB3+RQSpTtoM+sJyFOpzJG8ck nUGQ+ALm2CV7GFzUFlPG9cTgGN+FxwrBvyQQiV1mcfuGI48LsDxtxu0foLo9Gpmi6p2k uAMSHbJM2u1sdn4JQwctG1AvLlggLkF7Y8h0niyJcuEmwWzbEuqq3b/IwfKwcNyOB3L7 i0DQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=PMKaB0Oa5QXUNtHyl3wAgOjSQCtL7tLwsVttCyl931A=; b=cxSqgkN8F6LydFcSh8zbd1wgIJMgV+BZzey9vnYiHS363w+1/hdC8wqv0EavvtOup8 uwA0CSJ615kH0C9uAlxjmUie4h2jHHBHMyFqgbF2zn6vTUBR5BkeNQBagFsugnQXqeav 5KtZGBANTkTCn5jofNoIM6dLaxmFXrh42dffWGov7FtfPv2eYrySSywSG34t7LryPKxO jAYxyMDkYWCVIMc71NwPQzMC+6I5WExgTk8LrOSggVtGSoUYYCuuT245SDagJLLqU0VV CsGvhVdQ73sVqLfMvrttep+wrYVlrWx3Crc36k0APusfDWcpUUmcP95OWtFz+Xpdpqal sfdA== X-Gm-Message-State: APjAAAWFD4KYwmSWqQcsg33XekbDQa8+tx6Q/FmLOW1xVj/EuhsP4LAv e1M8ixkqO3YgQHdVM9q9ekg= X-Received: by 2002:a63:17:: with SMTP id 23mr48293837pga.206.1557993626669; Thu, 16 May 2019 01:00:26 -0700 (PDT) Received: from localhost.localdomain ([203.100.54.194]) by smtp.gmail.com with ESMTPSA id p7sm2051471pgb.92.2019.05.16.01.00.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 May 2019 01:00:26 -0700 (PDT) From: Yuyang Du To: peterz@infradead.org, will.deacon@arm.com, mingo@kernel.org Cc: bvanassche@acm.org, ming.lei@redhat.com, frederic@kernel.org, tglx@linutronix.de, boqun.feng@gmail.com, paulmck@linux.ibm.com, linux-kernel@vger.kernel.org, Yuyang Du Subject: [PATCH v2 01/17] locking/lockdep: Add lock type enum to explicitly specify read or write locks Date: Thu, 16 May 2019 15:59:59 +0800 Message-Id: <20190516080015.16033-2-duyuyang@gmail.com> X-Mailer: git-send-email 2.20.1 (Apple Git-117) In-Reply-To: <20190516080015.16033-1-duyuyang@gmail.com> References: <20190516080015.16033-1-duyuyang@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Add an enum to formalize lock types, as those type values now matter. In order to make: LOCK_TYPE_READ & LOCK_TYPE_RECURSIVE != 0 The recursive-read type is set to 3 as opposed to the current 2. Signed-off-by: Yuyang Du --- include/linux/lockdep.h | 45 +++++++++++++++++++++++++++++++++++++++------ include/linux/rcupdate.h | 2 +- kernel/locking/lockdep.c | 23 +++++++++++++---------- 3 files changed, 53 insertions(+), 17 deletions(-) diff --git a/include/linux/lockdep.h b/include/linux/lockdep.h index 7c2fefa..1009c47 100644 --- a/include/linux/lockdep.h +++ b/include/linux/lockdep.h @@ -339,10 +339,38 @@ static inline int lockdep_match_key(struct lockdep_map *lock, * * Values for "read": * - * 0: exclusive (write) acquire - * 1: read-acquire (no recursion allowed) - * 2: read-acquire with same-instance recursion allowed + * LOCK_TYPE_EXCLUSIVE (LOCK_TYPE_WRITE): exclusive (write) acquire + * LOCK_TYPE_READ: read-acquire (no recursion allowed) + * LOCK_TYPE_RECURSIVE: read-acquire with same-instance recursion allowed * + * The same lock between tasks have the following exclusiveness (the read + * type includes recursive read): + * + * read and read (no ) + * read and write (yes) + * write and write (yes) + * + * The enum values for the types are arranged such that: + * + * if type1 and type2 are exclusive then type1 & type2 == 0. + * + * We have a tricky situation concerning read vs. recursive-read. Since + * there can be lock classes that may ever be both read lock and + * recursive-read lock, for example: + * + * kernel/qrwlock.c:queued_read_lock_slowpath() + * + * The values of lock types are defined as follows: + */ +enum lock_type { + LOCK_TYPE_EXCLUSIVE = 0, + LOCK_TYPE_WRITE = 0, + LOCK_TYPE_READ, + LOCK_TYPE_UNUSED, + LOCK_TYPE_RECURSIVE, +}; + +/* * Values for check: * * 0: simple checks (freeing, held-at-exit-time, etc.) @@ -588,9 +616,14 @@ static inline void print_irqtrace_events(struct task_struct *curr) * on the per lock-class debug mode: */ -#define lock_acquire_exclusive(l, s, t, n, i) lock_acquire(l, s, t, 0, 1, n, i) -#define lock_acquire_shared(l, s, t, n, i) lock_acquire(l, s, t, 1, 1, n, i) -#define lock_acquire_shared_recursive(l, s, t, n, i) lock_acquire(l, s, t, 2, 1, n, i) +#define lock_acquire_exclusive(l, s, t, n, i) \ + lock_acquire(l, s, t, LOCK_TYPE_EXCLUSIVE, 1, n, i) + +#define lock_acquire_shared(l, s, t, n, i) \ + lock_acquire(l, s, t, LOCK_TYPE_READ, 1, n, i) + +#define lock_acquire_shared_recursive(l, s, t, n, i) \ + lock_acquire(l, s, t, LOCK_TYPE_RECURSIVE, 1, n, i) #define spin_acquire(l, s, t, i) lock_acquire_exclusive(l, s, t, NULL, i) #define spin_acquire_nest(l, s, t, n, i) lock_acquire_exclusive(l, s, t, n, i) diff --git a/include/linux/rcupdate.h b/include/linux/rcupdate.h index 922bb68..22b41b1 100644 --- a/include/linux/rcupdate.h +++ b/include/linux/rcupdate.h @@ -207,7 +207,7 @@ static inline void destroy_rcu_head_on_stack(struct rcu_head *head) { } static inline void rcu_lock_acquire(struct lockdep_map *map) { - lock_acquire(map, 0, 0, 2, 0, NULL, _THIS_IP_); + lock_acquire(map, 0, 0, LOCK_TYPE_RECURSIVE, 0, NULL, _THIS_IP_); } static inline void rcu_lock_release(struct lockdep_map *map) diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c index 7275d6c..fb6be63 100644 --- a/kernel/locking/lockdep.c +++ b/kernel/locking/lockdep.c @@ -2297,7 +2297,10 @@ static inline void inc_chains(void) * (Note that this has to be done separately, because the graph cannot * detect such classes of deadlocks.) * - * Returns: 0 on deadlock detected, 1 on OK, 2 on recursive read + * Returns: + * 0: on deadlock detected; + * 1: on OK; + * 3: LOCK_TYPE_RECURSIVE on recursive read */ static int check_deadlock(struct task_struct *curr, struct held_lock *next) @@ -2319,15 +2322,15 @@ static inline void inc_chains(void) * Allow read-after-read recursion of the same * lock class (i.e. read_lock(lock)+read_lock(lock)): */ - if ((next->read == 2) && prev->read) - return 2; + if ((next->read == LOCK_TYPE_RECURSIVE) && prev->read) + return LOCK_TYPE_RECURSIVE; /* * We're holding the nest_lock, which serializes this lock's * nesting behaviour. */ if (nest) - return 2; + return LOCK_TYPE_RECURSIVE; print_deadlock_bug(curr, prev, next); return 0; @@ -2407,7 +2410,7 @@ static inline void inc_chains(void) * write-lock never takes any other locks, then the reads are * equivalent to a NOP. */ - if (next->read == 2 || prev->read == 2) + if (next->read == LOCK_TYPE_RECURSIVE || prev->read == LOCK_TYPE_RECURSIVE) return 1; /* * Is the -> dependency already present? @@ -2493,7 +2496,7 @@ static inline void inc_chains(void) * Only non-recursive-read entries get new dependencies * added: */ - if (hlock->read != 2 && hlock->check) { + if (hlock->read != LOCK_TYPE_RECURSIVE && hlock->check) { int ret = check_prev_add(curr, hlock, next, distance, &trace); if (!ret) @@ -2877,13 +2880,13 @@ static int validate_chain(struct task_struct *curr, * building dependencies (just like we jump over * trylock entries): */ - if (ret == 2) - hlock->read = 2; + if (ret == LOCK_TYPE_RECURSIVE) + hlock->read = LOCK_TYPE_RECURSIVE; /* * Add dependency only if this lock is not the head * of the chain, and if it's not a secondary read-lock: */ - if (!chain_head && ret != 2) { + if (!chain_head && ret != LOCK_TYPE_RECURSIVE) { if (!check_prevs_add(curr, hlock)) return 0; } @@ -4105,7 +4108,7 @@ static int __lock_downgrade(struct lockdep_map *lock, unsigned long ip) curr->curr_chain_key = hlock->prev_chain_key; WARN(hlock->read, "downgrading a read lock"); - hlock->read = 1; + hlock->read = LOCK_TYPE_READ; hlock->acquire_ip = ip; if (reacquire_held_locks(curr, depth, i)) -- 1.8.3.1