diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2018-03-15 02:51:33 +0300 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2018-03-15 02:51:33 +0300 |
commit | fed8f5090ca647b7cf37c21f92053e517526133a (patch) | |
tree | 4cd2a81f2aa42c7636b263f02560b1b7b1af49f4 /lib | |
parent | 3e04040df6d4613a8af5a80882d5f7f298f49810 (diff) | |
parent | 74b44bbe80b4c62113ac1501482ea1ee40eb9d67 (diff) | |
download | linux-fed8f5090ca647b7cf37c21f92053e517526133a.tar.xz |
Merge branch 'percpu_ref-rcu-audit-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc
Pull percpu_ref rcu fixes from Tejun Heo:
"Jann Horn found that aio was depending on the internal RCU grace
periods of percpu-ref and that it's broken because aio uses regular
RCU while percpu_ref uses sched-RCU.
Depending on percpu_ref's internal grace periods isn't a good idea
because
- The RCU type might not match.
- percpu_ref's grace periods are used to switch to atomic mode. They
aren't between the last put and the invocation of the last release.
This is easy to get confused about and can lead to subtle bugs.
- percpu_ref might not have grace periods at all depending on its
current operation mode.
This patchset audits and fixes percpu_ref users for their RCU usages"
[ There's a continuation of this series that clarifies percpu_ref
documentation that the internal grace periods must not be depended
upon, and introduces rcu_work to simplify bouncing to a workqueue
after an RCU grace period.
That will go in for 4.17 - this is just the minimal set with the fixes
that are tagged for -stable ]
* 'percpu_ref-rcu-audit-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc:
RDMAVT: Fix synchronization around percpu_ref
fs/aio: Use RCU accessors for kioctx_table->table[]
fs/aio: Add explicit RCU grace period when freeing kioctx
Diffstat (limited to 'lib')
0 files changed, 0 insertions, 0 deletions