From: David Sterba <dsterba@suse.cz>
To: Nikolay Borisov <nborisov@suse.com>
Cc: stable@vger.kernel.org, Ethan Lien <ethanlien@synology.com>
Subject: Re: [PATCH] btrfs: use correct compare function of dirty_metadata_bytes
Date: Wed, 5 Sep 2018 11:18:00 +0200 [thread overview]
Message-ID: <20180905091800.GT24025@suse.cz> (raw)
In-Reply-To: <1535970598-25308-1-git-send-email-nborisov@suse.com>
On Mon, Sep 03, 2018 at 01:29:58PM +0300, Nikolay Borisov wrote:
> From: Ethan Lien <ethanlien@synology.com>
>
> We use customized, nodesize batch value to update dirty_metadata_bytes.
> We should also use batch version of compare function or we will easily
> goto fast path and get false result from percpu_counter_compare().
>
> Fixes: e2d845211eda ("Btrfs: use percpu counter for dirty metadata count")
> CC: stable@vger.kernel.org # 4.4+
> Signed-off-by: Ethan Lien <ethanlien@synology.com>
> Reviewed-by: Nikolay Borisov <nborisov@suse.com>
> Signed-off-by: David Sterba <dsterba@suse.com>
> [nb: Rebased on 4.9.y]
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
> ---
>
> Here is a 4.9.y backport of upstream commit:
> d814a49198eafa6163698bdd93961302f3a877a4
Please put this information to the changelog itself as the first line:
commit d814a49198eafa6163698bdd93961302f3a877a4 upstream.
next prev parent reply other threads:[~2018-09-05 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 16:45 FAILED: patch "[PATCH] btrfs: use correct compare function of dirty_metadata_bytes" failed to apply to 4.9-stable tree gregkh
2018-09-03 10:29 ` [PATCH] btrfs: use correct compare function of dirty_metadata_bytes Nikolay Borisov
2018-09-05 9:18 ` David Sterba [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-08-29 16:45 FAILED: patch "[PATCH] btrfs: use correct compare function of dirty_metadata_bytes" failed to apply to 4.4-stable tree gregkh
2018-09-03 10:26 ` [PATCH] btrfs: use correct compare function of dirty_metadata_bytes Nikolay Borisov
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=20180905091800.GT24025@suse.cz \
--to=dsterba@suse.cz \
--cc=ethanlien@synology.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;
as well as URLs for NNTP newsgroup(s).