From: Coly Li <colyli@suse.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-raid <linux-raid@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: bcache patches for Linux v5.18
Date: Sun, 6 Mar 2022 18:35:45 +0800 [thread overview]
Message-ID: <084b5385-ebe7-5fca-8b56-a66276005e78@suse.de> (raw)
Hi Jens,
I have technical problem to send patches via email this time, please
consider to pull the bcache changes from my bcache tree. They can be
applied on top of your for-5.18/drivers branch.
We have 2 patches for Linux v5.18, both of them are from Mingzhe Zou.
The first patch improves bcache initialization speed by avoid
unnecessary cost of cache consistency, the second one fixes a potential
NULL pointer deference in bcache initialization time,
Please take them for Linux v5.18, thanks in advance.
Coly Li
The following changes since commit dcde98da997075053041942ecf97d787855722ec:
Merge branch 'for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input (2022-03-05
15:49:45 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/colyli/linux-bcache.git/
for-next
for you to fetch changes up to 387ac428d163b6fffa923618624505e7afe0b53d:
bcache: fixup multiple threads crash (2022-03-06 18:14:43 +0800)
----------------------------------------------------------------
Mingzhe Zou (2):
bcache: fixup bcache_dev_sectors_dirty_add() multithreaded CPU
false sharing
bcache: fixup multiple threads crash
drivers/md/bcache/btree.c | 6 ++++--
drivers/md/bcache/writeback.c | 17 +++++++++++------
2 files changed, 15 insertions(+), 8 deletions(-)
next reply other threads:[~2022-03-06 10:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 10:35 Coly Li [this message]
2022-03-06 14:17 ` bcache patches for Linux v5.18 Jens Axboe
2022-03-06 14:55 ` Coly Li
2022-03-06 15:15 ` Jens Axboe
2022-03-06 15:53 ` Coly Li
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=084b5385-ebe7-5fca-8b56-a66276005e78@suse.de \
--to=colyli@suse.de \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-raid@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