Jorgen Lundman

Also, the nested kfpu_begin() calls seem to have been cleaned up, so I can probably get rid of kfpu_vars

OK, so changes to compile on macOS in shared files: https://github.com/openzfsonosx/openzfs-fork/commit/256294a5c163ed3866ab98e51c79b17405095715 and changes to macOS files: https://github.com/openzfsonosx/openzfs-fork/commit/2f12e628e72fb65efe85e9b16d2dc487f789d1a2 adding aesv8 https://github.com/openzfsonosx/openzfs-fork/commit/ae7a8aca06ace75fe37ab4a13a300b5935c645d2

The keylocation is generally what ZOL guys do. I know some guys had success storing key in the KeyChain, but I'm not sure how far they got with that.

Ah hmm, that is awkward indeed. Wonder if you could have it not-empty, then force mount over (even though ZFS don't like it), or mount it as union ontop. I've...

I'd curious how it is implemented in these apps. They might be referring to hard links, which are hard to detect once you make them. macOS does have fcntls for...

Last two seem OK ``` # Start with a source file to link against $ cp macos_zfs /Volumes/BOOM/source.bin # Create some links to point to it $ ln source.bin linkA.bin...

It can return `resource temporarily unavailable (error 35)` if `clonefile()` is done "too quickly" after the file is created, avoided with a `zpool sync` between. Newer macOS will use `clonefile()`...

Looks like we should pull in https://github.com/openzfs/zfs/pull/15842

The best thing would be to run `sudo spindump` when it has happened, it will show which thread(s) are busy and what they are doing.

I believe it doesn't happen on the new port, as that is handled differently... maybe