From: Jens Axboe <axboe@kernel.dk>
To: Michael Lyle <mlyle@lyle.org>
Cc: linux-bcache@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: Series of patches for bcache targeting 4.15
Date: Mon, 30 Oct 2017 15:58:23 -0600 [thread overview]
Message-ID: <20171030215821.GA17465@kernel.dk> (raw)
In-Reply-To: <20171030214635.29888-1-mlyle@lyle.org>
On Mon, Oct 30 2017, Michael Lyle wrote:
> Hi Jens--
>
> I have a few last patches for bcache targeting 4.15 if it's
> possible to get them in. I'm sorry this is a bit late.
>
> All are reviewed and have received a moderate amount of test
> in my environment (and I'm continuing testing).
>
> [PATCH 1/5] bcache: only permit to recovery read error when cache
> [PATCH 2/5] bcache: convert cached_dev.count from atomic_t to
> [PATCH 3/5] bcache: update bucket_in_use in real time
> [PATCH 4/5] bcache: fix wrong cache_misses statistics
> [PATCH 5/5] bcache: explicitly destroy mutex while exiting
>
> Patches 1 and 3 are critical. The first fixes correctness problems
> if a cache volume fails and is being carried in distro trees. #3
> prevents a rare issue that can cause extended hanging of end-user
> I/O. The other three patches are relatively safe cleanup.
Thanks, applied for 4.15.
--
Jens Axboe
prev parent reply other threads:[~2017-10-30 21:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 21:46 Series of patches for bcache targeting 4.15 Michael Lyle
2017-10-30 21:46 ` [PATCH 1/5] bcache: only permit to recovery read error when cache device is clean Michael Lyle
2017-10-30 21:46 ` [PATCH 2/5] bcache: convert cached_dev.count from atomic_t to refcount_t Michael Lyle
2017-10-30 21:46 ` [PATCH 3/5] bcache: update bucket_in_use in real time Michael Lyle
2017-10-30 21:46 ` [PATCH 4/5] bcache: fix wrong cache_misses statistics Michael Lyle
2017-10-30 21:46 ` [PATCH 5/5] bcache: explicitly destroy mutex while exiting Michael Lyle
2017-10-30 21:58 ` Jens Axboe [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=20171030215821.GA17465@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=mlyle@lyle.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).