Well, problems with contracts, laws, etc. is that they are created (we enter into them, ...) because we want something. But while doing so, some written document is produced and from that point, one big problem starts: we try to adhere to the agreement, law, whatever but some stuff can be evaluated in two different ways with two opposing results depending on whether you are interpreting "the spirit" of the contract, law, ... or "the letter".
I guess, dynamically linked kernel extensions ... are against "the spirit" of GPL (any GPL, not just v3). But such judgement will have to be individually handed out (at least by me, if i'm asked to :) depending also on what the module does, how it does that, who produced it, what is the intention of the producer, ...
All that is complex. So, "in a spirit" of what I wrote earlier, I try to avoid such "complicated matters".
Thus, I did not follow closely the debate you are referring to. I just noted "yup, there are issues, mainly if you try to make a profit off of GPL licensed code". So my commercial work .. I simply avoid GPLv3 code - good for the company, good for the authors of the GPLv3 licensed code in question too.
My opinion (also as a developer of commercial software) is, that GPLv3 is mostly "controversial", "bad", ... for those who for some reason try not to follow "the spirit", but "the letter" of that license. Maybe because they do not understand the free/open source movement. Or because they are trying to profit from the GPLv3 licensed works of others without without giving equally back.
But again, in some individual cases, such "harsh" opinion might be deadly wrong.