From: Stefan Priebe Date: Sat, 16 Nov 2013 20:26:52 +0000 (+0100) Subject: bcache: kthread don't set writeback task to INTERUPTIBLE X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=f665c0f852316ff99e9eb7f71f34d43003f8e139;p=GitHub%2FLineageOS%2Fandroid_kernel_motorola_exynos9610.git bcache: kthread don't set writeback task to INTERUPTIBLE at the beginning (schedule_timout_interuptible) and others do his on their own This prevents wrong load average calculation (load of 1 per thread) Signed-off-by: Kent Overstreet --- diff --git a/drivers/md/bcache/writeback.c b/drivers/md/bcache/writeback.c index 99053b1251be..484e57d7012c 100644 --- a/drivers/md/bcache/writeback.c +++ b/drivers/md/bcache/writeback.c @@ -500,8 +500,6 @@ int bch_cached_dev_writeback_init(struct cached_dev *dc) if (IS_ERR(dc->writeback_thread)) return PTR_ERR(dc->writeback_thread); - set_task_state(dc->writeback_thread, TASK_INTERRUPTIBLE); - INIT_DELAYED_WORK(&dc->writeback_rate_update, update_writeback_rate); schedule_delayed_work(&dc->writeback_rate_update, dc->writeback_rate_update_seconds * HZ);