Page MenuHomeFreeBSD

Report max protection for vm_map_entry in ptrace(PTRACE_VM_ENTRY) and kinfo_vmentry
ClosedPublic

Authored by kib on Mon, Oct 7, 8:38 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Nov 1, 11:25 AM
Unknown Object (File)
Thu, Oct 31, 3:54 PM
Unknown Object (File)
Wed, Oct 23, 1:10 PM
Unknown Object (File)
Sun, Oct 13, 10:34 AM
Unknown Object (File)
Tue, Oct 8, 1:43 PM
Unknown Object (File)
Tue, Oct 8, 6:50 AM
Unknown Object (File)
Mon, Oct 7, 8:31 PM
Unknown Object (File)
Mon, Oct 7, 7:06 PM
Subscribers

Details

Summary

procstat bits are not included, I think it will go as a separate column in procstat vm output, hidden under a flag to not break the output format by default

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

kib requested review of this revision.Mon, Oct 7, 8:38 AM

procstat bits are not included, I think it will go as a separate column in procstat vm output, hidden under a flag to not break the output format by default

In CheriBSD, procstat vm has a -v option to enable some extra columns, so I would suggest using that for maxprot.

This revision is now accepted and ready to land.Mon, Oct 7, 12:05 PM
sys/sys/user.h
509–511

I'd rather these start from 0x00010000 like PROT_MAX(PROT_READ). We've added two additional port bits in CheriBSD and it would be annoying to interleave MAX and regular PROTs.

This revision now requires review to proceed.Tue, Oct 8, 6:27 AM
kib marked an inline comment as done.Tue, Oct 8, 6:27 AM
This revision is now accepted and ready to land.Tue, Oct 8, 6:33 AM