diff options
author | Ahmed S. Darwish <a.darwish@linutronix.de> | 2020-07-20 18:55:18 +0300 |
---|---|---|
committer | Peter Zijlstra <peterz@infradead.org> | 2020-07-29 17:14:25 +0300 |
commit | cd29f22019ec4ab998d2e1e8c831c7c42db4aa7d (patch) | |
tree | 1785abfcb60364439ddc19a3f9a7d54b5afb13b1 /net/netfilter/nf_conntrack_core.c | |
parent | 318ce71f3e3ae4108c1665f3860afa8a2a4c9f02 (diff) | |
download | linux-cd29f22019ec4ab998d2e1e8c831c7c42db4aa7d.tar.xz |
dma-buf: Use sequence counter with associated wound/wait mutex
A sequence counter write side critical section must be protected by some
form of locking to serialize writers. If the serialization primitive is
not disabling preemption implicitly, preemption has to be explicitly
disabled before entering the sequence counter write side critical
section.
The dma-buf reservation subsystem uses plain sequence counters to manage
updates to reservations. Writer serialization is accomplished through a
wound/wait mutex.
Acquiring a wound/wait mutex does not disable preemption, so this needs
to be done manually before and after the write side critical section.
Use the newly-added seqcount_ww_mutex_t instead:
- It associates the ww_mutex with the sequence count, which enables
lockdep to validate that the write side critical section is properly
serialized.
- It removes the need to explicitly add preempt_disable/enable()
around the write side critical section because the write_begin/end()
functions for this new data type automatically do this.
If lockdep is disabled this ww_mutex 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>
Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Link: https://lkml.kernel.org/r/20200720155530.1173732-13-a.darwish@linutronix.de
Diffstat (limited to 'net/netfilter/nf_conntrack_core.c')
0 files changed, 0 insertions, 0 deletions