From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Filipe Manana <fdmanana@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 1/2] Btrfs: fix race between ranged fsync and writeback of adjacent ranges
Date: Mon, 06 May 2019 17:18:54 +0000 [thread overview]
Message-ID: <20190506171855.0BCAA2053B@mail.kernel.org> (raw)
In-Reply-To: <20190506154402.20097-1-fdmanana@kernel.org>
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: 3.16+
The bot has tested the following trees: v5.0.13, v4.19.40, v4.14.116, v4.9.173, v4.4.179, v3.18.139.
v5.0.13: Build OK!
v4.19.40: Build OK!
v4.14.116: Build OK!
v4.9.173: Build OK!
v4.4.179: Build OK!
v3.18.139: Failed to apply! Possible dependencies:
9dcbeed4d7e1 ("btrfs: fix signed overflows in btrfs_sync_file")
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-05-06 17:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 15:44 [PATCH 1/2] Btrfs: fix race between ranged fsync and writeback of adjacent ranges fdmanana
2019-05-06 17:18 ` Sasha Levin [this message]
2019-05-07 17:44 ` Josef Bacik
2019-05-07 19:09 ` Filipe Manana
2019-05-07 19:31 ` Josef Bacik
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=20190506171855.0BCAA2053B@mail.kernel.org \
--to=sashal@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