diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2025-10-23 09:26:47 -1000 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2025-10-23 09:26:47 -1000 |
commit | 266ee584e55eed108583ab4f45b5de734522502d (patch) | |
tree | efa2221863e7edb02b2fad69818c0f3b86577f53 /drivers/scsi/pcmcia | |
parent | ab431bc39741e9d9bd3102688439e1864c857a74 (diff) | |
parent | b98c94eed4a975e0c80b7e90a649a46967376f58 (diff) |
Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linuxHEADtorvalds/mastertorvalds/HEADmaster
Pull arm64 fixes from Catalin Marinas:
- Do not make a clean PTE dirty in pte_mkwrite()
The Arm architecture, for backwards compatibility reasons (ARMv8.0
before in-hardware dirty bit management - DBM), uses the PTE_RDONLY
bit to mean !dirty while the PTE_WRITE bit means DBM enabled. The
arm64 pte_mkwrite() simply clears the PTE_RDONLY bit and this
inadvertently makes the PTE pte_hw_dirty(). Most places making a PTE
writable also invoke pte_mkdirty() but do_swap_page() does not and we
end up with dirty, freshly swapped in, writeable pages.
- Do not warn if the destination page is already MTE-tagged in
copy_highpage()
In the majority of the cases, a destination page copied into is
freshly allocated without the PG_mte_tagged flag set. However, the
folio migration may be restarted if __folio_migrate_mapping() failed,
triggering the benign WARN_ON_ONCE().
* tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux:
arm64: mte: Do not warn if the page is already tagged in copy_highpage()
arm64, mm: avoid always making PTE dirty in pte_mkwrite()
Diffstat (limited to 'drivers/scsi/pcmcia')
0 files changed, 0 insertions, 0 deletions