OSDN Git Service

vfs: Use sequence counter with associated spinlock
authorAhmed S. Darwish <a.darwish@linutronix.de>
Mon, 20 Jul 2020 15:55:24 +0000 (17:55 +0200)
committerPeter Zijlstra <peterz@infradead.org>
Wed, 29 Jul 2020 14:14:27 +0000 (16:14 +0200)
commit26475371976c69489d3a8e6c8bbf35afbbc25055
tree5f7ac08bbe80ab13cd56cd4dcf0cdf4d6829d061
parent025e82bcbc34cd071390e72fd0b31593282f9425
vfs: Use sequence counter with associated spinlock

A sequence counter write side critical section must be protected by some
form of locking to serialize writers. A plain seqcount_t does not
contain the information of which lock must be held when entering a write
side critical section.

Use the new seqcount_spinlock_t data type, which allows to associate a
spinlock with the sequence counter. This enables lockdep to verify that
the spinlock used for writer serialization is held when the write side
critical section is entered.

If lockdep is disabled this lock association is compiled out and has
neither storage size nor runtime overhead.

Signed-off-by: Ahmed S. Darwish <a.darwish@linutronix.de>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lkml.kernel.org/r/20200720155530.1173732-19-a.darwish@linutronix.de
fs/dcache.c
fs/fs_struct.c
include/linux/dcache.h
include/linux/fs_struct.h