What to do in response to a kernel warning

Looking at the WARN_ONs I've experienced here in the last half-decade, I had warnings on boot for about two years because of amdgpu multi-monitor problems which eventually got fixed: but while they were happening, reboot-on-warn would have been precisely the wrong thing to do because the warnings didn't actually ever cause anything to go wrong that I could tell. I had warnings on minor bcache gc problems which might cause, at most, a leak of a single bucket (4MiB) which in any case would go away upon the next gc after reboot: there's no *way* that sort of thing would ever be worthy of a reboot unless it hit almost every bucket (it didn't, it hit one out of ~90k), but a WARN_ON was used because, well, it's worthy of a warning, right? In this case the warning was likely used as a "please tell the developer" flag, probably on the grounds that anything less would just be ignored.

The only warning I ever had that was actually worthwhile was a warning from xfs which was immediately afterwards followed by a verifier failure flipping the affected fs to readonly. This was entirely correct given that it would otherwise have resulted in fs corruption -- but I'm fairly sure a reboot would not have been preferable to the readonly-flipping it already did (though in the event the affected fs happened to be the rootfs, so there was little else I could do: but that need not have been the case).

So, so far, here at least, the number of WARNs that should have resulted in a reboot is, uh, 0%.