On Fri, Sep 28, 2018 at 02:15:09PM -0700, Andrew Morton wrote: > What did he report? Was it code inspection? Did the kernel explode? > etcetera. I'm thinking that the fix should be backported but to > determine that, we need to understand the end-user runtime effects, as > always. Please. I've been investigating unrelated but and occasionally found this nit. Look, there should be over 4G of objects scanned to have it triggered, so I don't expect it happen in real life but better be on a safe side and fix it.