From: Coly Li <colyli@suse.de>
To: axboe@kernel.dk
Cc: linux-bcache@vger.kernel.org, linux-block@vger.kernel.org,
Coly Li <colyli@suse.de>
Subject: [PATCH 0/5] bcache patches for Linux v5.6-rc1
Date: Sat, 1 Feb 2020 22:42:30 +0800 [thread overview]
Message-ID: <20200201144235.94110-1-colyli@suse.de> (raw)
Hi Jens,
Here are the bcache patches for Linux v5.6-rc1. All the patches are
tested and survived my I/O pressure tests for 24+ hours intotal.
Please take them. Thank you in advance.
Coly Li
---
Coly Li (5):
bcache: fix memory corruption in bch_cache_accounting_clear()
bcache: explicity type cast in bset_bkey_last()
bcache: add readahead cache policy options via sysfs interface
bcache: fix incorrect data type usage in btree_flush_write()
bcache: check return value of prio_read()
drivers/md/bcache/bcache.h | 3 +++
drivers/md/bcache/bset.h | 3 ++-
drivers/md/bcache/journal.c | 3 ++-
drivers/md/bcache/request.c | 17 ++++++++++++-----
drivers/md/bcache/stats.c | 10 +++++++---
drivers/md/bcache/super.c | 21 ++++++++++++++++-----
drivers/md/bcache/sysfs.c | 22 ++++++++++++++++++++++
7 files changed, 64 insertions(+), 15 deletions(-)
--
2.16.4
next reply other threads:[~2020-02-01 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 14:42 Coly Li [this message]
2020-02-01 14:42 ` [PATCH 1/5] bcache: fix memory corruption in bch_cache_accounting_clear() Coly Li
2020-02-01 14:42 ` [PATCH 2/5] bcache: explicity type cast in bset_bkey_last() Coly Li
2020-02-01 14:42 ` [PATCH 3/5] bcache: add readahead cache policy options via sysfs interface Coly Li
2020-02-01 14:42 ` [PATCH 4/5] bcache: fix incorrect data type usage in btree_flush_write() Coly Li
2020-02-01 14:42 ` [PATCH 5/5] bcache: check return value of prio_read() Coly Li
2020-02-01 14:58 ` [PATCH 0/5] bcache patches for Linux v5.6-rc1 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=20200201144235.94110-1-colyli@suse.de \
--to=colyli@suse.de \
--cc=axboe@kernel.dk \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.