But we're not talking about non-NMI code. The 8k referred to in the
original patch are buffers used by NMI stack recording. Module code
vmalloc_sync_all() is only need by code that is executed during NMI,
hence must be NMI aware.
"fixing NMI" will result in code that is understandable by maybe three
people after long and hard thinking. NMI can happen in too many
semi-defined contexts, so there will be plenty of edge cases. I'm not
sure we can ever trust such trickery.
If NMI code can call random hooks and access random data, yes. But I
don't think we're at that point yet.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--