This is a note to let you know that I've just added the patch titled

    reiserfs: destroy allocated commit workqueue

to the 3.18-stable tree which can be found at:
    
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     reiserfs-destroy-allocated-commit-workqueue.patch
and it can be found in the queue-3.18 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.


>From fa0c5540739320258c3e3a45aaae9dae467b2504 Mon Sep 17 00:00:00 2001
From: Jiri Slaby <[email protected]>
Date: Fri, 12 Dec 2014 16:29:29 +0100
Subject: reiserfs: destroy allocated commit workqueue
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

From: Jiri Slaby <[email protected]>

commit fa0c5540739320258c3e3a45aaae9dae467b2504 upstream.

When resirefs is trying to mount a partition, it creates a commit
workqueue (sbi->commit_wq). But when mount fails later, the workqueue
is not freed.

Signed-off-by: Jiri Slaby <[email protected]>
Reported-by: [email protected]
Reported-by: BenoĆ®t Monin <[email protected]>
Cc: Jan Kara <[email protected]>
Cc: [email protected]
Fixes: 797d9016ceca69879bb273218810fa0beef46aac
Signed-off-by: Jan Kara <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
 fs/reiserfs/super.c |    3 +++
 1 file changed, 3 insertions(+)

--- a/fs/reiserfs/super.c
+++ b/fs/reiserfs/super.c
@@ -2161,6 +2161,9 @@ error_unlocked:
                reiserfs_write_unlock(s);
        }
 
+       if (sbi->commit_wq)
+               destroy_workqueue(sbi->commit_wq);
+
        cancel_delayed_work_sync(&REISERFS_SB(s)->old_work);
 
        reiserfs_free_bitmap_cache(s);


Patches currently in stable-queue which might be from [email protected] are

queue-3.18/reiserfs-destroy-allocated-commit-workqueue.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to