From: Jiri Slaby <jslaby@suse.cz>
To: reiserfs-devel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Jan Kara <jack@suse.cz>,
All Versions <stable@vger.kernel.org>,
Jeff Mahoney <jeffm@suse.com>
Subject: Re: [PATCH 1/1] reiserfs: destroy allocated commit workqueue
Date: Fri, 12 Dec 2014 17:02:07 +0100 [thread overview]
Message-ID: <548B117F.7090509@suse.cz> (raw)
In-Reply-To: <1418398169-19820-1-git-send-email-jslaby@suse.cz>
On 12/12/2014, 04:29 PM, Jiri Slaby wrote:
> 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 <jslaby@suse.cz>
> Reported-by: auxsvr@gmail.com
> Reported-by: Benoît Monin <benoit.monin@gmx.fr>
> Cc: Jan Kara <jack@suse.cz>
> Cc: All Versions <stable@vger.kernel.org>
This is not quite correct. It was introduced in commit
797d9016ceca69879bb273218810fa0beef46aac (reiserfs: use per-fs commit
workqueues), so only 3.16+ is affected.
> Cc: reiserfs-devel@vger.kernel.org
> ---
> fs/reiserfs/super.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/fs/reiserfs/super.c b/fs/reiserfs/super.c
> index ea63ab13ef92..71fbbe3e2dab 100644
> --- a/fs/reiserfs/super.c
> +++ b/fs/reiserfs/super.c
> @@ -2172,6 +2172,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);
>
--
js
suse labs
next prev parent reply other threads:[~2014-12-12 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 15:29 [PATCH 1/1] reiserfs: destroy allocated commit workqueue Jiri Slaby
2014-12-12 16:02 ` Jiri Slaby [this message]
2014-12-12 21:27 ` Jan Kara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=548B117F.7090509@suse.cz \
--to=jslaby@suse.cz \
--cc=jack@suse.cz \
--cc=jeffm@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).