summaryrefslogtreecommitdiffstats
path: root/kernel/time/tick-internal.h
diff options
context:
space:
mode:
authorRik van Riel <riel@surriel.com>2024-05-07 09:18:58 -0400
committerAndrew Morton <akpm@linux-foundation.org>2024-05-11 15:51:44 -0700
commit5cbcb62dddf5346077feb82b7b0c9254222d3445 (patch)
treeaad879165860d3672e7ecfa11720d7cc73578890 /kernel/time/tick-internal.h
parent0a73eac1ed10097d1799c10dff2172605fd40c75 (diff)
downloadlinux-5cbcb62dddf5346077feb82b7b0c9254222d3445.tar.gz
linux-5cbcb62dddf5346077feb82b7b0c9254222d3445.tar.bz2
linux-5cbcb62dddf5346077feb82b7b0c9254222d3445.zip
fs/proc: fix softlockup in __read_vmcore
While taking a kernel core dump with makedumpfile on a larger system, softlockup messages often appear. While softlockup warnings can be harmless, they can also interfere with things like RCU freeing memory, which can be problematic when the kdump kexec image is configured with as little memory as possible. Avoid the softlockup, and give things like work items and RCU a chance to do their thing during __read_vmcore by adding a cond_resched. Link: https://lkml.kernel.org/r/20240507091858.36ff767f@imladris.surriel.com Signed-off-by: Rik van Riel <riel@surriel.com> Acked-by: Baoquan He <bhe@redhat.com> Cc: Dave Young <dyoung@redhat.com> Cc: Vivek Goyal <vgoyal@redhat.com> Cc: <stable@vger.kernel.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'kernel/time/tick-internal.h')
0 files changed, 0 insertions, 0 deletions