From: Jens Axboe <axboe@kernel.dk>
To: colyli@suse.de
Cc: linux-bcache@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [Resend PATCH v2 0/4] bcache fixes for Linux v5.19 (1st wave)
Date: Tue, 24 May 2022 06:19:54 -0600 [thread overview]
Message-ID: <165339479414.6179.11008749918880416100.b4-ty@kernel.dk> (raw)
In-Reply-To: <20220524102336.10684-1-colyli@suse.de>
On Tue, 24 May 2022 18:23:32 +0800, Coly Li wrote:
> Thank you for taking the late arrived series, they are all for bcache
> fixes when I work on the bcache journal no-space deadlock issue. It
> spent me quite long time to fix because other issues interfered my debug
> and analysis. When all the depending issues were fixed and my fix for
> the journal no-space deadlock is verified, this submission is late for
> Linux v5.19 submission. But it is still worthy to take them into v5.19
> because real issues are fixed by this series.
>
> [...]
Applied, thanks!
[1/4] bcache: improve multithreaded bch_btree_check()
commit: 622536443b6731ec82c563aae7807165adbe9178
[2/4] bcache: improve multithreaded bch_sectors_dirty_init()
commit: 4dc34ae1b45fe26e772a44379f936c72623dd407
[3/4] bcache: remove incremental dirty sector counting for bch_sectors_dirty_init()
commit: 80db4e4707e78cb22287da7d058d7274bd4cb370
[4/4] bcache: avoid journal no-space deadlock by reserving 1 journal bucket
commit: 32feee36c30ea06e38ccb8ae6e5c44c6eec790a6
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-05-24 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 10:23 [Resend PATCH v2 0/4] bcache fixes for Linux v5.19 (1st wave) Coly Li
2022-05-24 10:23 ` [PATCH 1/4] bcache: improve multithreaded bch_btree_check() Coly Li
2022-05-24 10:23 ` [PATCH 2/4] bcache: improve multithreaded bch_sectors_dirty_init() Coly Li
2022-05-24 10:23 ` [PATCH 3/4] bcache: remove incremental dirty sector counting for bch_sectors_dirty_init() Coly Li
2022-05-24 10:23 ` [PATCH 4/4] bcache: avoid journal no-space deadlock by reserving 1 journal bucket Coly Li
2022-05-24 12:19 ` 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=165339479414.6179.11008749918880416100.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=colyli@suse.de \
--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.