diff options
| author | Linus Torvalds <[email protected]> | 2020-06-01 13:03:31 -0700 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2020-06-01 13:03:31 -0700 |
| commit | 60056060bede58c3073dccb8a5e73a6c40804aa9 (patch) | |
| tree | 93097df99142146627f5c01d01cdab77a271185a /kernel/bpf/syscall.c | |
| parent | 2227e5b21aec6c5f7f6491352f0c19fd02d19418 (diff) | |
| parent | 19f545b6e07f753c4dc639c2f0ab52345733b6a8 (diff) | |
Merge tag 'locking-core-2020-06-01' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull locking updates from Ingo Molnar:
"The biggest change to core locking facilities in this cycle is the
introduction of local_lock_t - this primitive comes from the -rt
project and identifies CPU-local locking dependencies normally handled
opaquely beind preempt_disable() or local_irq_save/disable() critical
sections.
The generated code on mainline kernels doesn't change as a result, but
still there are benefits: improved debugging and better documentation
of data structure accesses.
The new local_lock_t primitives are introduced and then utilized in a
couple of kernel subsystems. No change in functionality is intended.
There's also other smaller changes and cleanups"
* tag 'locking-core-2020-06-01' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
zram: Use local lock to protect per-CPU data
zram: Allocate struct zcomp_strm as per-CPU memory
connector/cn_proc: Protect send_msg() with a local lock
squashfs: Make use of local lock in multi_cpu decompressor
mm/swap: Use local_lock for protection
radix-tree: Use local_lock for protection
locking: Introduce local_lock()
locking/lockdep: Replace zero-length array with flexible-array
locking/rtmutex: Remove unused rt_mutex_cmpxchg_relaxed()
Diffstat (limited to 'kernel/bpf/syscall.c')
0 files changed, 0 insertions, 0 deletions