Page MenuHomeFreeBSD

ipf: copy{in,out}ptr -> ipf_copy{in,out}_indirect
Needs ReviewPublic

Authored by brooks on Mon, Dec 15, 1:50 PM.
Tags
None
Referenced Files
F139855142: D54232.id168200.diff
Wed, Dec 17, 3:47 AM
F139855098: D54232.diff
Wed, Dec 17, 3:46 AM
Unknown Object (File)
Mon, Dec 15, 10:52 PM
Unknown Object (File)
Mon, Dec 15, 9:46 PM

Details

Reviewers
cy
Group Reviewers
cheri
Summary

These functions take the source or destintation address indirectly from
a potentially missaligned buffer. Rename them to refect this and to
free up the copy{in,out}ptr names.

Some of the code in question is dead code and doesn't or won't compile,
but I've changed it all for consistency.

NB: If the pointers are actually stored under aligned then this code is
broken with CHERI.

Effort: CHERI upstreaming
Sponsored by: Innovate UK

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 69303
Build 66186: arc lint + arc unit

Event Timeline

These names aren't generic and I'd like to use them for copy{in,out} variants that explicitly preserve pointer provenance as part of the CHERI import (we currently use copy{in,out}cap in CheriBSD to preserved pointer provenance when pointers are implemented as CHERI capabilities, but think it's better to talk about pointers rather than capabilities which have too many meanings even within the tree.)

Why not properly namespace these with an ipf_ prefix whilst you're at it?

This revision is now accepted and ready to land.Mon, Dec 15, 9:18 PM

Why not properly namespace these with an ipf_ prefix whilst you're at it?

Good point.

brooks retitled this revision from ipf: copy{in,out}ptr -> copy{in,out}_indirect to ipf: copy{in,out}ptr -> ipf_copy{in,out}_indirect.Tue, Dec 16, 4:15 PM

prefix functions with ipf_

This revision now requires review to proceed.Tue, Dec 16, 4:15 PM