Page MenuHomeFreeBSD

Make vop_symlink take a const target path.
ClosedPublic

Authored by brooks on Nov 1 2018, 4:27 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Nov 18, 12:21 PM
Unknown Object (File)
Sun, Nov 17, 5:02 AM
Unknown Object (File)
Mon, Nov 4, 9:58 AM
Unknown Object (File)
Wed, Oct 30, 7:35 PM
Unknown Object (File)
Mon, Oct 28, 11:31 PM
Unknown Object (File)
Sat, Oct 26, 8:17 AM
Unknown Object (File)
Oct 21 2024, 11:01 AM
Unknown Object (File)
Oct 21 2024, 5:58 AM
Subscribers

Details

Summary

This will enable callers to take const paths as part of syscall
decleration improvements.

Where doing so is easy and non-distruptive carry the const through
implementations. In UFS the value is passed to an interface that must
take non-const values. In ZFS, const poisoning would touch code shared
with upstream and it's not worth adding diffs.

Test Plan

tinderbox build, build kmod ports

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision is now accepted and ready to land.Nov 1 2018, 5:49 PM
  • Update the VOP_SYMLINK signature in the manpage.
This revision now requires review to proceed.Nov 1 2018, 10:05 PM
  • Add missed __DECONST in nandfs.
  • Rebase
  • Bump __FreeBSD_version for external API consumers.

With the nandfs fix this passes universe. I've done a search for vop_symlink on https://grok.dragonflybsd.org and concluded that an exp-run isn't going to find anything so I'll skip that.

This revision was not accepted when it landed; it landed in state Needs Review.Nov 2 2018, 2:43 PM
This revision was automatically updated to reflect the committed changes.