diff options
| author | Sebastian Andrzej Siewior <bigeasy@linutronix.de> | 2014-02-17 17:30:03 +0100 |
|---|---|---|
| committer | Clark Williams <williams@redhat.com> | 2018-03-29 09:51:08 -0500 |
| commit | 6dea0835f2d0d280fe696ff0b3b04b5cdd61855d (patch) | |
| tree | a324f3105b2237729e39098d84670cb4607d2770 | |
| parent | ee6f35a4c9181df63d36f681a301a800b32e367f (diff) | |
| download | rt-linux-6dea0835f2d0d280fe696ff0b3b04b5cdd61855d.tar.gz | |
fs: jbd2: pull your plug when waiting for space
Two cps in parallel managed to stall the the ext4 fs. It seems that
journal code is either waiting for locks or sleeping waiting for
something to happen. This seems similar to what Mike observed on ext3,
here is his description:
|With an -rt kernel, and a heavy sync IO load, tasks can jam
|up on journal locks without unplugging, which can lead to
|terminal IO starvation. Unplug and schedule when waiting
|for space.
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
| -rw-r--r-- | fs/jbd2/checkpoint.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/fs/jbd2/checkpoint.c b/fs/jbd2/checkpoint.c index c125d662777c67..67367c9a6835a6 100644 --- a/fs/jbd2/checkpoint.c +++ b/fs/jbd2/checkpoint.c @@ -113,6 +113,8 @@ void __jbd2_log_wait_for_space(journal_t *journal) nblocks = jbd2_space_needed(journal); while (jbd2_log_space_left(journal) < nblocks) { write_unlock(&journal->j_state_lock); + if (current->plug) + io_schedule(); mutex_lock(&journal->j_checkpoint_mutex); /* |