spl

They are sometimes very good at using mathematical identities to do simplifications. The following commit was actually inspired by the output of GCC: https://github.com/openzfs/spl/commit/8fc851b7b5315c9cae9255... Jason had noticed that GCC’s assembly output did not match the original macro when looking for a solution to the unsigned integer overflow warning that a PaX GCC plugin had output (erroneously in my opinion). He had conjectured we could safely adopt GCC’s version as a workaround. I gave him the proof of correctness for the commit message and it was accepted into ZFS. As you can see from the proof, deriving that from the original required 4 steps. I assume that GCC had gone through a similar process to derive its output.

No, I mean SPL[1]. The linux devs definitely don't want a proliferation of porting interfaces mucking up the kernel tree, so unless the OpenZFS devs want to work on a Linux specific port, I don't see ZFS getting mainlined regardless of the licensing issue. CDDL certainly doesn't help to make this happen though. Also "Empty threats are void" is a silly stance to take; betting that nobody who will own copyright to code in the CDDL is going to sue anytime in the next 80ish years would be dumb even ignoring the fact that Oracle owns copyright to at least some of that code right now, and they are quite litigious. 1: https://github.com/openzfs/spl