Advertising

Ok, great, a - mostly - false alarm.
I do wonder if we should just remove even that WARN_ON_ONCE() - I
think it was added to be careful, and the code seems to do the right
thing.
The second WARN_ON_ONCE() (that is marked as "should be impossible")
we might as well leave around. If that one triggers, it's a lot more
interesting.
Mel? No hurry - the nice thing about WARN_ON_ONCE() is that it's just
a single note so it's neither killing the machine(*) nor causing any
real problems.
Linus
(*) when it works, but presumably it is now fixed on ARM64, and I
expect I'll see a pull request ;).