All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Sergei Trofimovich <slyich@gmail.com>
Cc: Sergei Trofimovich <slyfox@gentoo.org>, Chris Mason <clm@fb.com>,
	Josef Bacik <jbacik@fb.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs: fix crash in remount(thread_pool=) case
Date: Tue, 8 Apr 2014 09:28:10 +0800	[thread overview]
Message-ID: <534350AA.8030209@cn.fujitsu.com> (raw)
In-Reply-To: <1396857346-24877-1-git-send-email-slyich@gmail.com>


于 2014年04月07日 15:55, Sergei Trofimovich 写道:
> From: Sergei Trofimovich <slyfox@gentoo.org>
>
> Reproducer:
>      mount /dev/ubda /mnt
>      mount -oremount,thread_pool=42 /mnt
>
> Gives a crash:
>      ? btrfs_workqueue_set_max+0x0/0x70
>      btrfs_resize_thread_pool+0xe3/0xf0
>      ? sync_filesystem+0x0/0xc0
>      ? btrfs_resize_thread_pool+0x0/0xf0
>      btrfs_remount+0x1d2/0x570
>      ? kern_path+0x0/0x80
>      do_remount_sb+0xd9/0x1c0
>      do_mount+0x26a/0xbf0
>      ? kfree+0x0/0x1b0
>      SyS_mount+0xc4/0x110
>
> It's a call
>      btrfs_workqueue_set_max(fs_info->scrub_wr_completion_workers, new_pool_size);
> with
>      fs_info->scrub_wr_completion_workers = NULL;
>
> as scrub wqs get created only on user's demand.
>
> Patch skips not-created-yet workqueues.
>
> Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
> CC: Qu Wenruo <quwenruo@cn.fujitsu.com>
> CC: Chris Mason <clm@fb.com>
> CC: Josef Bacik <jbacik@fb.com>
> CC: linux-btrfs@vger.kernel.org
>
> ---
>   fs/btrfs/async-thread.c | 2 ++
>   1 file changed, 2 insertions(+)
>
> diff --git a/fs/btrfs/async-thread.c b/fs/btrfs/async-thread.c
> index ecb5832..5a201d8 100644
> --- a/fs/btrfs/async-thread.c
> +++ b/fs/btrfs/async-thread.c
> @@ -323,6 +323,8 @@ void btrfs_destroy_workqueue(struct btrfs_workqueue *wq)
>   
>   void btrfs_workqueue_set_max(struct btrfs_workqueue *wq, int max)
>   {
> +	if (!wq)
> +		return;
>   	wq->normal->max_active = max;
>   	if (wq->high)
>   		wq->high->max_active = max;
Oh, that's my fault. You got me.

Thanks for the patch.
Qu.

      reply	other threads:[~2014-04-08  1:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07  7:55 [PATCH] btrfs: fix crash in remount(thread_pool=) case Sergei Trofimovich
2014-04-08  1:28 ` Qu Wenruo [this message]

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=534350AA.8030209@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.com \
    --cc=clm@fb.com \
    --cc=jbacik@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=slyfox@gentoo.org \
    --cc=slyich@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.