diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2014-04-28 00:08:12 +0200 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2014-04-28 00:08:12 +0200 |
commit | ac6c9e2bed093c4b60e313674fb7aec4f264c3d4 (patch) | |
tree | 6eccadffcc04a7b66021ab3bd114cafcb52181c6 /include/asm-generic/word-at-a-time.h | |
parent | Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mas... (diff) | |
parent | mm: split 'tlb_flush_mmu()' into tlb flushing and memory freeing parts (diff) | |
download | linux-ac6c9e2bed093c4b60e313674fb7aec4f264c3d4.tar.xz linux-ac6c9e2bed093c4b60e313674fb7aec4f264c3d4.zip |
Merge branch 'safe-dirty-tlb-flush'
This merges the patch to fix possible loss of dirty bit on munmap() or
madvice(DONTNEED). If there are concurrent writers on other CPU's that
have the unmapped/unneeded page in their TLBs, their writes to the page
could possibly get lost if a third CPU raced with the TLB flush and did
a page_mkclean() before the page was fully written.
Admittedly, if you unmap() or madvice(DONTNEED) an area _while_ another
thread is still busy writing to it, you deserve all the lost writes you
could get. But we kernel people hold ourselves to higher quality
standards than "crazy people deserve to lose", because, well, we've seen
people do all kinds of crazy things.
So let's get it right, just because we can, and we don't have to worry
about it.
* safe-dirty-tlb-flush:
mm: split 'tlb_flush_mmu()' into tlb flushing and memory freeing parts
Diffstat (limited to 'include/asm-generic/word-at-a-time.h')
0 files changed, 0 insertions, 0 deletions