Page MenuHomeFreeBSD

Make vadvise compat freebsd11.
ClosedPublic

Authored by brooks on May 24 2018, 5:16 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, May 5, 12:34 AM
Unknown Object (File)
Thu, May 2, 12:10 AM
Unknown Object (File)
Mon, Apr 29, 9:36 PM
Unknown Object (File)
Mon, Apr 29, 1:57 AM
Unknown Object (File)
Mar 31 2024, 2:44 AM
Unknown Object (File)
Mar 9 2024, 7:17 AM
Unknown Object (File)
Feb 29 2024, 10:43 PM
Unknown Object (File)
Jan 29 2024, 3:35 AM
Subscribers

Details

Summary

The vadvise syscall (aka ovadvise) is undocumented and has always been
implmented as returning EINVAL. Put the syscall under COMPAT11 and
provide a userspace implementation.

Diff Detail

Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 16814
Build 16697: arc lint + arc unit

Event Timeline

Could you, please, remove the generated files from the review and from the commit ?

  • Remove generated files from review.

Add a dependency cleanup in Makefile.inc1 after commit also?

lib/libc/sys/vadvise.c
5

holder?

  • Actually name copyright holder.

Add a dependency cleanup in Makefile.inc1 after commit also?

That's the plan.

lib/libc/sys/vadvise.c
39

Are __sys_vadvise and _vadvise symbols used by anything in the base system ? If no, then they can be removed, since we do not provide stable ABI in FreeBSD private namespace.

sys/vm/vm_unix.c
240–241

I believe this structure definition is useless.

  • Nothing uses _vadvise() or __sys_vadvise so don't provide them.
  • Don't document ignored struct freebsd11_vadvise_args.
This revision is now accepted and ready to land.May 24 2018, 7:03 PM
This revision was automatically updated to reflect the committed changes.