On 2020/07/16 21:21, Michal Hocko wrote: > If the oom report should be misleading then it would be better to not > bother at all IMHO. From my experience the memory state is really useful > when debugging ooms and having a reasonable snapshot is really > important. IIRC Tetsuo was suggesting collecting all the information at > the time of the oom and print that snapshot later on but the patch was > quite invasive and didn't handle multiple OOMs from different oom > domains - especially the dump_task part would need to link all the tasks > for different oom contexts. I did, and you just refused as always. https://lore.kernel.org/linux-mm/20190830103504.GA28313@xxxxxxxxxxxxxx/ https://lore.kernel.org/linux-mm/20190909113627.GJ27159@xxxxxxxxxxxxxx/
