When to use the new FSExtentType.readOnly?

App & System Services Core OS
kthchew OP
Created 8h
Replies 1
Boosts 0
Views 42
Participants 2
This post is from the WWDC26 File Systems Q&A.

Is it necessary to switch to the new FSExtentType.readOnly when implementing kernel offloaded IO if my entire volume is read-only and marked as such via requestedMountOptions?

(My assumption is "no" since I'd think all writes to the resource at that point should be prevented anyway, but wanted to ask just in case.)

Answered by Apple Staff in 891079022

No, there is no need to do that. That extent type indicates to the kernel side that another blockmap operation needs to be done for any write request to that range.

Replies  1
Boosts  0
Views  42
Participants  2
Apple Staff OP
Apple
8h
Accepted Answer
Recommended

No, there is no need to do that. That extent type indicates to the kernel side that another blockmap operation needs to be done for any write request to that range.

When to use the new FSExtentType.readOnly?
First post date Last post date
 
 
Q