History

perf: MAP_EXECUTABLE does not indicate VM_MAYEXEC

Patch series "perf/binfmt/mm: remove in-tree usage of MAP_EXECUTABLE". Stumbling over the history of MAP_EXECUTABLE, I noticed that we still have some in-tree users that we can get rid of. This patch (of 3): Before commit e9714acf8c43 ("mm: kill vma flag VM_EXECUTABLE and mm->num_exe_file_vmas"), VM_EXECUTABLE indicated MAP_EXECUTABLE. MAP_EXECUTABLE is nowadays essentially ignored by the kernel and does not relate to VM_MAYEXEC.

David Hildenbrand committed 5 years ago

Commit 8fa20751 parent 6a1803b1 file · +0 −2Browse files

Showing the changes to kernel (1 of 1 file). Show all

Unified · Split

kernel/events/core.c+0−2
@@ -8301,8 +8301,6 @@ static void perf_event_mmap_event(struct perf_mmap_event *mmap_event) · 8300 unmodified lines
83018301
83028302 if (vma->vm_flags & VM_DENYWRITE)
83038303 flags |= MAP_DENYWRITE;
8304− if (vma->vm_flags & VM_MAYEXEC)
8305− flags |= MAP_EXECUTABLE;
83068304 if (vma->vm_flags & VM_LOCKED)
83078305 flags |= MAP_LOCKED;
83088306 if (is_vm_hugetlb_page(vma))

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t