btrfs: always choose work from prio_head first
authorStanislaw Gruszka <stf_xl@wp.pl>
Sat, 8 Feb 2014 22:18:43 +0000 (23:18 +0100)
committerJosef Bacik <jbacik@fb.com>
Mon, 10 Mar 2014 19:16:36 +0000 (15:16 -0400)
In case we do not refill, we can overwrite cur pointer from prio_head
by one from not prioritized head, what looks as something that was
not intended.

This change make we always take works from prio_head first until it's
not empty.

Signed-off-by: Stanislaw Gruszka <stf_xl@wp.pl>
Signed-off-by: Josef Bacik <jbacik@fb.com>
fs/btrfs/async-thread.c

index c1e0b0caf9cc975c2822cadf9aaaf0c1454dcf91..0b78bf28ff5daf06b9b4ca92caa5d56f6b375a60 100644 (file)
@@ -262,18 +262,19 @@ static struct btrfs_work *get_next_work(struct btrfs_worker_thread *worker,
        struct btrfs_work *work = NULL;
        struct list_head *cur = NULL;
 
-       if (!list_empty(prio_head))
+       if (!list_empty(prio_head)) {
                cur = prio_head->next;
+               goto out;
+       }
 
        smp_mb();
        if (!list_empty(&worker->prio_pending))
                goto refill;
 
-       if (!list_empty(head))
+       if (!list_empty(head)) {
                cur = head->next;
-
-       if (cur)
                goto out;
+       }
 
 refill:
        spin_lock_irq(&worker->lock);