Page MenuHomeFreeBSD

factor out the code that actually does the truncation from vn_truncate() into vn_truncate_locked()
ClosedPublic

Authored by rmacklem on Jun 30 2019, 12:26 AM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Dec 24, 3:18 PM
Unknown Object (File)
Mon, Dec 22, 6:03 AM
Unknown Object (File)
Sun, Dec 21, 4:04 AM
Unknown Object (File)
Thu, Dec 11, 10:19 PM
Unknown Object (File)
Nov 29 2025, 1:47 PM
Unknown Object (File)
Nov 20 2025, 9:39 PM
Unknown Object (File)
Nov 20 2025, 9:37 PM
Unknown Object (File)
Nov 20 2025, 9:37 PM
Subscribers

Details

Summary

This patch factors out the code that actually does the truncation from vn_truncate() into vn_truncate_locked().
This will allow vn_truncate_locked() to be called within the NFS server and by D20584 for the copy_file_range(2) syscall,
instead of needing to carry across any changes (such as the recent r347151) made to vn_truncate() over to the NFS
server code (and copy_file_range(2) when added to head.

There should be no semantic change to vn_truncate().

Test Plan

Tested using a program that calls the truncate(2) syscall and a program I use to test copy_file_range(2) for a
sparse file.

Diff Detail

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