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
| ||
|
Date: Sun, 14 Mar 2010 19:38:44 +0900 From: Hitoshi Mitake <mitake@....info.waseda.ac.jp> To: fweisbec@...il.com Cc: linux-kernel@...r.kernel.org, mitake@....info.waseda.ac.jp, h.mitake@...il.com, Ingo Molnar <mingo@...e.hu>, Peter Zijlstra <a.p.zijlstra@...llo.nl>, Paul Mackerras <paulus@...ba.org>, Arnaldo Carvalho de Melo <acme@...hat.com>, Jens Axboe <jens.axboe@...cle.com>, Jason Baron <jbaron@...hat.com> Subject: [PATCH RFC 07/11] Adopt the way of initializing semaphore to lock monitor Now spinlock_t doesn't have struct lockdep_map, this was replaced with struct lock_monitor. So this patch fixes the way of initializing semaphore. Signed-off-by: Hitoshi Mitake <mitake@....info.waseda.ac.jp> Cc: Ingo Molnar <mingo@...e.hu> Cc: Peter Zijlstra <a.p.zijlstra@...llo.nl> Cc: Paul Mackerras <paulus@...ba.org> Cc: Arnaldo Carvalho de Melo <acme@...hat.com> Cc: Jens Axboe <jens.axboe@...cle.com> Cc: Jason Baron <jbaron@...hat.com> --- include/linux/semaphore.h | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/include/linux/semaphore.h b/include/linux/semaphore.h index 7415839..d5aa2ba 100644 --- a/include/linux/semaphore.h +++ b/include/linux/semaphore.h @@ -33,7 +33,7 @@ static inline void sema_init(struct semaphore *sem, int val) { static struct lock_class_key __key; *sem = (struct semaphore) __SEMAPHORE_INITIALIZER(*sem, val); - lockdep_init_map(&sem->lock.dep_map, "semaphore->lock", &__key, 0); + lockdep_init_map(&sem->lock.monitor.dep_map, "semaphore->lock", &__key, 0); } #define init_MUTEX(sem) sema_init(sem, 1) -- 1.6.5.2 -- 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