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
F133294084: D20808.id59288.diff
Fri, Oct 24, 5:17 PM
Unknown Object (File)
Thu, Oct 23, 5:35 AM
Unknown Object (File)
Thu, Oct 23, 5:35 AM
Unknown Object (File)
Thu, Oct 23, 5:35 AM
Unknown Object (File)
Wed, Oct 22, 9:32 PM
Unknown Object (File)
Mon, Oct 6, 3:02 AM
Unknown Object (File)
Fri, Oct 3, 9:56 PM
Unknown Object (File)
Thu, Oct 2, 4:38 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