Linux-bcache Archive mirror
 help / color / mirror / Atom feed
From: Coly Li <colyli@suse.de>
To: axboe@kernel.dk
Cc: linux-block@vger.kernel.org, linux-bcache@vger.kernel.org,
	Coly Li <colyli@suse.de>
Subject: [PATCH 00/10] bcache-next 20231120
Date: Mon, 20 Nov 2023 13:24:53 +0800	[thread overview]
Message-ID: <20231120052503.6122-1-colyli@suse.de> (raw)

Hi Jens,

Here are recent bcache patches tested by me on Linux v6.7-rc1 and can be
applied on branch block-6.7 of linux-block tree. 

In this series, Colin provids useful code cleanup, some small and still
important fixes are contributed from Mingzhe, Rand. Also there are some
fixes and a code comments patch from me.

When I fixed the issue found during testing, 6.7-rc1 was released. IMHO
it still makes sense to have most of the fixes into 6.7. Please consider
to take them in block-6.7 if it is possible.

Thanks in advance.

Coly Li
---

Colin Ian King (1):
  bcache: remove redundant assignment to variable cur_idx

Coly Li (5):
  bcache: avoid oversize memory allocation by small stripe_size
  bcache: check return value from btree_node_alloc_replacement()
  bcache: replace a mistaken IS_ERR() by IS_ERR_OR_NULL() in
    btree_gc_coalesce()
  bcache: add code comments for bch_btree_node_get() and
    __bch_btree_node_alloc()
  bcache: avoid NULL checking to c->root in run_cache_set()

Mingzhe Zou (3):
  bcache: fixup init dirty data errors
  bcache: fixup lock c->root error
  bcache: fixup multi-threaded bch_sectors_dirty_init() wake-up race

Rand Deeb (1):
  bcache: prevent potential division by zero error

 drivers/md/bcache/bcache.h    |  1 +
 drivers/md/bcache/btree.c     | 11 ++++++++++-
 drivers/md/bcache/super.c     |  4 +++-
 drivers/md/bcache/sysfs.c     |  2 +-
 drivers/md/bcache/writeback.c | 24 ++++++++++++++++++------
 5 files changed, 33 insertions(+), 9 deletions(-)

-- 
2.35.3


             reply	other threads:[~2023-11-20  5:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20  5:24 Coly Li [this message]
2023-11-20  5:24 ` [PATCH 01/10] bcache: avoid oversize memory allocation by small stripe_size Coly Li
2023-11-20  5:24 ` [PATCH 02/10] bcache: check return value from btree_node_alloc_replacement() Coly Li
2023-11-20  5:24 ` [PATCH 03/10] bcache: remove redundant assignment to variable cur_idx Coly Li
2023-11-20  5:24 ` [PATCH 04/10] bcache: prevent potential division by zero error Coly Li
2023-11-20  5:24 ` [PATCH 05/10] bcache: fixup init dirty data errors Coly Li
2023-11-20  5:24 ` [PATCH 06/10] bcache: fixup lock c->root error Coly Li
2023-11-20  5:25 ` [PATCH 07/10] bcache: fixup multi-threaded bch_sectors_dirty_init() wake-up race Coly Li
2023-11-20  5:25 ` [PATCH 08/10] bcache: replace a mistaken IS_ERR() by IS_ERR_OR_NULL() in btree_gc_coalesce() Coly Li
2023-11-20  5:25 ` [PATCH 09/10] bcache: add code comments for bch_btree_node_get() and __bch_btree_node_alloc() Coly Li
2023-11-20  5:25 ` [PATCH 10/10] bcache: avoid NULL checking to c->root in run_cache_set() Coly Li
2023-11-20 16:18 ` [PATCH 00/10] bcache-next 20231120 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=20231120052503.6122-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 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 read-only IMAP folder(s) and NNTP newsgroup(s).