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)
Tue, Apr 21, 1:37 PM
Unknown Object (File)
Apr 15 2026, 3:14 AM
Unknown Object (File)
Apr 13 2026, 11:17 AM
Unknown Object (File)
Apr 12 2026, 6:48 PM
Unknown Object (File)
Apr 11 2026, 11:47 PM
Unknown Object (File)
Apr 10 2026, 10:43 AM
Unknown Object (File)
Apr 9 2026, 6:00 PM
Unknown Object (File)
Apr 2 2026, 1:06 AM
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