It's perhaps a moot point. Canonical have been distributing OpenZFS binaries for going on two years even though the FSF and the SFLC believe them to be in violation of the GPL. Angry blog posts doesn't cut it. The nature of law and precedent is that unless the FSF or SFLC sue Canonical Ltd. soonish for their distribution of OpenZFS Linux modules, their assertion that the GPL doesn't generally apply to kernel modules…
Keep in mind that (a) the FSF uses copyright assignment for many projects, which would put it in a legal position to pursue infringements for those projects, but Linux is not one of those projects; (b) the SFLC is a legal organisation, not a software developer, so they only pursue infringements on behalf of client projects; as far as I'm aware, Linux is not one of their clients.
I've not waded too far into this before, but from reading http://softwarefreedom.org/resources/2016/linux-kernel-cddl.... it seems to me that:
- Canonical distributes Linux+ZFS binaries under the GPLv2.
- As per the GPLv2, Canonical must provide the corresponding source, also under the GPLv2.
- The ZFS source is under the CDDL, which permits relicensing binaries (hence it's compatible with the first point) but not relicensing of the source, which is incompatible with the second point.
- Hence Canonical can either provide Linux+ZFS source under the GPLv2, violating the source's CDDL; or provide Linux source under GPLv2 and ZFS source under CDDL, violating the binary's GPLv2; or stop distributing Linux+ZFS binaries. They chose the second option.
- Since CDDL and GPLv2 are both copyleft FOSS licenses, this incompatibility is arguably a technicality since it doesn't violate the "spirit" of either license, and may be ignored at the copyright owner's discretion.
- The copyright owners of Linux seem to be ignoring it, which is fine.
So I don't see what the big deal is. By acting in this way, Canonical improve the usability of their distro, whilst they and their users/customers incur the risk that some day, potentially, they might have to change their config to build the module separately (like Debian does).