diff options
| author | Sean Christopherson <sean.j.christopherson@intel.com> | 2018-12-28 11:33:28 +0300 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2018-12-28 23:11:46 +0300 |
| commit | 6a90a83f1d1957647581ca48caa1f7cc4fa44f8d (patch) | |
| tree | 7a76c7b1232ce57f9d6b429d22ed236d0b503e76 /include/linux/seccomp.h | |
| parent | 5eb570a8d9248e0c1358078a59916d0e337e695b (diff) | |
| download | linux-6a90a83f1d1957647581ca48caa1f7cc4fa44f8d.tar.xz | |
mm/mmu_notifier.c: remove mmu_notifier_synchronize()
Contrary to its name, mmu_notifier_synchronize() does not synchronize the
notifier's SRCU instance, but rather waits for RCU callbacks to finish.
i.e. it invokes rcu_barrier(). The RCU documentation is quite clear on
this matter, explicitly calling out that rcu_barrier() does not imply
synchronize_rcu().
As there are no callers of mmu_notifier_synchronize() and it's unclear
whether any user of mmu_notifier_call_srcu() will ever want to barrier on
their callbacks, simply remove the function.
Link: http://lkml.kernel.org/r/20181106134705.14197-1-sean.j.christopherson@intel.com
Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com>
Reviewed-by: Andrew Morton <akpm@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Jérôme Glisse <jglisse@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include/linux/seccomp.h')
0 files changed, 0 insertions, 0 deletions