From: Qu Wenruo <quwenruo@cn.fujitsu.com>
Date: Thu, 20 Aug 2015 01:30:39 +0000 (+0800)
Subject: btrfs: async_thread: Fix workqueue 'max_active' value when initializing
X-Git-Tag: omap-for-v4.3/fixes-rc1~30^2~1
X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=c6dd6ea55758cf403bdc07a51a06c2a1d474f906;p=pandora-kernel.git

btrfs: async_thread: Fix workqueue 'max_active' value when initializing

At initializing time, for threshold-able workqueue, it's max_active
of kernel workqueue should be 1 and grow if it hits threshold.

But due to the bad naming, there is both 'max_active' for kernel
workqueue and btrfs workqueue.
So wrong value is given at workqueue initialization.

This patch fixes it, and to avoid further misunderstanding, change the
member name of btrfs_workqueue to 'current_active' and 'limit_active'.

Also corresponding comment is added for readability.

Reported-by: Alex Lyakas <alex.btrfs@zadarastorage.com>
Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
Signed-off-by: Chris Mason <clm@fb.com>
---

Reading git-diff-tree failed