stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] btrfs: don't needlessly create extent-refs kernel thread
Date: Sat, 12 Oct 2019 15:47:47 -0400	[thread overview]
Message-ID: <20191012194746.tuphjubvfeimy523@MacBook-Pro-91.local> (raw)
In-Reply-To: <20191012164210.17081-1-dsterba@suse.com>

On Sat, Oct 12, 2019 at 06:42:10PM +0200, David Sterba wrote:
> The patch 32b593bfcb58 ("Btrfs: remove no longer used function to run
> delayed refs asynchronously") removed the async delayed refs but the
> thread has been created, without any use. Remove it to avoid resource
> consumption.
> 
> Fixes: 32b593bfcb58 ("Btrfs: remove no longer used function to run delayed refs asynchronously")
> CC: stable@vger.kernel.org # 5.2+
> Signed-off-by: David Sterba <dsterba@suse.com>

Reviewed-by: Josef Bacik <josef@toxicpanda.com>

Thanks,

Josef

      reply	other threads:[~2019-10-12 19:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-12 16:42 [PATCH] btrfs: don't needlessly create extent-refs kernel thread David Sterba
2019-10-12 19:47 ` Josef Bacik [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=20191012194746.tuphjubvfeimy523@MacBook-Pro-91.local \
    --to=josef@toxicpanda.com \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@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).