to quote one commenter there:

there's something socially wrong with taking someone's gift and ignoring the terms under which it was given. If you want a system where you can load any modules, use a BSD kernel. [...] If the creators of a GPL kernel label some items as an external API for anyone's use, and other items as GPL hooks for functionally internal code loaded externally, respect that.

me talking about "protection" is a call for solutions. if the interpretation of the GPL here is absurd, then the problem is not that it is wrong, but that the GPL does not provide enough protection. if you don' want that protection, fine, that's your choice. i do want that protection, and i am looking for solutions. if you are not interested in solving that problem then we don't need to continue this discussion.

> you may want to read the discussion "Is the GPL actually viral across dynamic linking?"

What does that have to do with the price of tea in China? We are talking about an independent implementation of a BSD driver for Ext4-strucutred storage but you keep bringing up unrelated random pieces of chatter from around the web.

> but that the GPL does not provide enough protection.

But you don't understand the difference between copyright and contract. The GPL, or any other license based on copyright, cannot prevent the creation of the driver in question because it doesn't involve any copying of the kind protected by copyright law.

> if you are not interested in solving that problem then we don't need to continue this discussion.

Except, that's not the problem we are discussing.

Indeed, there's no point in continuing this discussion, you don't understand the basics, cannot follow the line of reasoning and keep getting lost in hallucinations.