Hi,
I met this too when I executed below command to trigger a kcore reading. I wanted to do a simple testing during system running and got this. makedumpfile --mem-usage /proc/kcore Later I tried your above objdump testing, it corrupted system too.
What do you mean with "corrupted system too" -- did it not only fail to dump the system, but also actually harmed the system?
@Lorenzo do you plan on reproduce + fix, or should we consider reverting that change?
-- Cheers, David / dhildenb
