From: Sasha Levin <sashal@kernel.org>
To: Nikolay Borisov <nborisov@suse.com>
Cc: gregkh@linuxfoundation.org, stable@vger.kernel.org,
Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>
Subject: Re: [PATCH] btrfs: release metadata before running delayed refs
Date: Mon, 3 Dec 2018 10:51:38 -0500 [thread overview]
Message-ID: <20181203155138.GJ235790@sasha-vm> (raw)
In-Reply-To: <20181203110657.24935-1-nborisov@suse.com>
On Mon, Dec 03, 2018 at 01:06:57PM +0200, Nikolay Borisov wrote:
>From: Josef Bacik <josef@toxicpanda.com>
>
>We want to release the unused reservation we have since it refills the
>delayed refs reserve, which will make everything go smoother when
>running the delayed refs if we're short on our reservation.
>
>CC: stable@vger.kernel.org # 4.4+
>Reviewed-by: Omar Sandoval <osandov@fb.com>
>Reviewed-by: Liu Bo <bo.liu@linux.alibaba.com>
>Reviewed-by: Nikolay Borisov <nborisov@suse.com>
>Signed-off-by: Josef Bacik <josef@toxicpanda.com>
>Signed-off-by: David Sterba <dsterba@suse.com>
>---
>
>Hi Greg,
>
>Please apply this backport of upstream commit f45c752b65af46bf42963295c332865d95f97fff
>to 4.14.y.
I've queued this one for 4.14, and the one you previously sent to 4.9
and 4.4. Thank you.
--
Thanks,
Sasha
prev parent reply other threads:[~2018-12-03 15:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-11 20:19 FAILED: patch "[PATCH] btrfs: release metadata before running delayed refs" failed to apply to 4.4-stable tree gregkh
2018-11-20 8:11 ` [PATCH 1/3] btrfs: release metadata before running delayed refs Nikolay Borisov
2018-11-29 12:21 ` Greg KH
2018-11-29 12:36 ` Nikolay Borisov
2018-12-03 10:01 ` Greg KH
2018-12-03 15:50 ` Sasha Levin
2018-12-12 11:41 ` Nikolay Borisov
2018-12-03 11:06 ` [PATCH] " Nikolay Borisov
2018-12-03 15:51 ` Sasha Levin [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=20181203155138.GJ235790@sasha-vm \
--to=sashal@kernel.org \
--cc=dsterba@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=josef@toxicpanda.com \
--cc=nborisov@suse.com \
--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