aboutsummaryrefslogtreecommitdiff
path: root/linux/dev/kernel
diff options
context:
space:
mode:
authorSergey Bugaev <bugaevc@gmail.com>2024-04-05 18:18:49 +0300
committerSamuel Thibault <samuel.thibault@ens-lyon.org>2024-04-05 17:44:59 +0200
commit6e5e1f09ef6e1ae0b92d38f0c7960ef3fed9f63b (patch)
tree286a4cecab3ba0480cedf1b50e8300aa4388a82b /linux/dev/kernel
parent7b87e10b89a190bca0d9e6c5e183984411840dc3 (diff)
downloadgnumach-6e5e1f09ef6e1ae0b92d38f0c7960ef3fed9f63b.tar.gz
gnumach-6e5e1f09ef6e1ae0b92d38f0c7960ef3fed9f63b.tar.bz2
gnumach-6e5e1f09ef6e1ae0b92d38f0c7960ef3fed9f63b.zip
vm: Don't attempt to extend in-transition entries
The in-transition mechanism exists to make it possible to unlock a map while still making sure some VM entries won't disappear from under you. This is currently used by the VM copyin mechanics. Entries in this state are better left alone, and extending/coalescing is only an optimization, so it makes sense to skip it if the entry to be extended is in transition. vm_map_coalesce_entry() already checks for this; check for it in other similar places too. This is in preparation for using the in-transition mechanism for wiring, where it's much more important that the entries are not extended while in transition. Message-ID: <20240405151850.41633-2-bugaevc@gmail.com>
Diffstat (limited to 'linux/dev/kernel')
0 files changed, 0 insertions, 0 deletions