Now that we disable wbt by simply zero out rwb->wb_normal in
wbt_disable_default() when switch elevator to bfq, but it's not safe
because it will become false positive if we change queue depth. If it
become false positive between wbt_wait() and wbt_track() when submit
write request, it will lead to drop rqw->inflight to -1 in wbt_done(),
which will end up trigger IO hung. Fix this issue by introduce a new
state which mean the wbt was disabled.
Fixes: a79050434b45 ("blk-rq-qos: refactor out common elements of blk-wbt")
Signed-off-by: Zhang Yi <yi.zhang@huawei.com>
Link: https://lore.kernel.org/r/20210619093700.920393-2-yi.zhang@huawei.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
 
 static inline bool rwb_enabled(struct rq_wb *rwb)
 {
-       return rwb && rwb->wb_normal != 0;
+       return rwb && rwb->enable_state != WBT_STATE_OFF_DEFAULT &&
+                     rwb->wb_normal != 0;
 }
 
 static void wb_timestamp(struct rq_wb *rwb, unsigned long *var)
        rwb = RQWB(rqos);
        if (rwb->enable_state == WBT_STATE_ON_DEFAULT) {
                blk_stat_deactivate(rwb->cb);
-               rwb->wb_normal = 0;
+               rwb->enable_state = WBT_STATE_OFF_DEFAULT;
        }
 }
 EXPORT_SYMBOL_GPL(wbt_disable_default);
 
 enum {
        WBT_STATE_ON_DEFAULT    = 1,
        WBT_STATE_ON_MANUAL     = 2,
+       WBT_STATE_OFF_DEFAULT
 };
 
 struct rq_wb {