From: Coly Li <colyli@suse.de>
To: axboe@kernel.dk
Cc: linux-bcache@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, hch@lst.de,
Coly Li <colyli@suse.de>
Subject: [PATCH v2 0/2] bcache fixes for Linux v5.13-rc6
Date: Mon, 7 Jun 2021 20:50:50 +0800 [thread overview]
Message-ID: <20210607125052.21277-1-colyli@suse.de> (raw)
Hi Jens,
This series is important for recent reported bcache panic partially
triggered by recent bio changes since Linux v5.12.
Current fix is 5th version since the first effort, it might not be
perfect yet, but it survives from different workloads from Rolf,
Thorsten and me for more than 1 week in total.
Considering many people are waiting for a stable enough fix and it is
kind of such fix. Please take them for Linux v5.13-rc6.
Thank you in advance for taking care of them.
Coly Li
---
Series changelog:
v2, update with comments from Christoph Hellwig.
v1, initial submission for v5.13-rc6.
Coly Li (2):
bcache: remove bcache device self-defined readahead
bcache: avoid oversized read request in cache missing code path
drivers/md/bcache/bcache.h | 1 -
drivers/md/bcache/request.c | 20 +++++++-------------
drivers/md/bcache/stats.c | 14 --------------
drivers/md/bcache/stats.h | 1 -
drivers/md/bcache/sysfs.c | 4 ----
5 files changed, 7 insertions(+), 33 deletions(-)
--
2.26.2
next reply other threads:[~2021-06-07 12:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 12:50 Coly Li [this message]
2021-06-07 12:50 ` [PATCH 1/2] bcache: remove bcache device self-defined readahead Coly Li
2021-06-07 12:50 ` [PATCH 2/2] bcache: avoid oversized read request in cache missing code path Coly Li
2021-06-08 16:46 ` [PATCH v2 0/2] bcache fixes for Linux v5.13-rc6 Coly Li
2021-06-08 21:06 ` Jens Axboe
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=20210607125052.21277-1-colyli@suse.de \
--to=colyli@suse.de \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@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).