| 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: <1426655010-31651-1-git-send-email-tom.yeon@windriver.com> Date: Wed, 18 Mar 2015 14:03:30 +0900 From: "Tom(JeHyeon) Yeon" <tomyeon750415lkml@...il.com> To: peterz@...radead.org, mingo@...hat.com Cc: linux-kernel@...r.kernel.org, "Tom(JeHyeon) Yeon" <tom.yeon@...driver.com> Subject: [PATCH] rtmutex: Cleanup the variable's name in rt_mutex_adjust_prio_chain From: "Tom(JeHyeon) Yeon" <tom.yeon@...driver.com> change "deadlock_detect" to "chwalk" following by commit 8930ed80 Signed-off-by: Tom(JeHyeon) Yeon <tom.yeon@...driver.com> --- kernel/locking/rtmutex.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/locking/rtmutex.c b/kernel/locking/rtmutex.c index 6357265..b732793 100644 --- a/kernel/locking/rtmutex.c +++ b/kernel/locking/rtmutex.c @@ -349,7 +349,7 @@ static inline struct rt_mutex *task_blocked_on_lock(struct task_struct *p) * * @task: the task owning the mutex (owner) for which a chain walk is * probably needed - * @deadlock_detect: do we have to carry out deadlock detection? + * @chwalk: do we have to carry out deadlock detection? * @orig_lock: the mutex (can be NULL if we are walking the chain to recheck * things for a task that has just got its priority adjusted, and * is waiting on a mutex) -- 1.7.9.5 -- 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