aboutsummaryrefslogtreecommitdiffstats
path: root/fs/fs-writeback.c
diff options
context:
space:
mode:
authorArtem Bityutskiy <Artem.Bityutskiy@nokia.com>2010-07-25 14:29:14 +0300
committerJens Axboe <jaxboe@fusionio.com>2010-08-07 18:53:55 +0200
commitc4ec7908c2c5125f75fabd100e7a95626a6883ee (patch)
treed58ee401205de8385c74a04e9b66101fc9a6e22b /fs/fs-writeback.c
parentc5f7ad233b8805dae06e694538d8095b19f3c560 (diff)
downloadmrst-s0i3-test-c4ec7908c2c5125f75fabd100e7a95626a6883ee.tar.gz
mrst-s0i3-test-c4ec7908c2c5125f75fabd100e7a95626a6883ee.tar.xz
mrst-s0i3-test-c4ec7908c2c5125f75fabd100e7a95626a6883ee.zip
writeback: do not lose wake-ups in the forker thread - 2
Currently, if someone submits jobs for the default bdi, we can lose wake-up events. E.g., this can happen if 'bdi_queue_work()' is called when 'bdi_forker_thread()' is executing code after 'wb_do_writeback(me, 0)', but before 'set_current_state(TASK_INTERRUPTIBLE)'. This situation is unlikely, and the result is not very severe - we'll just delay the execution of the work, but this is still not very nice. This patch fixes the issue by checking whether the default bdi has works before the forker thread goes sleep. Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com> Reviewed-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Jens Axboe <jaxboe@fusionio.com>
Diffstat (limited to 'fs/fs-writeback.c')
0 files changed, 0 insertions, 0 deletions