From: Jens Axboe <axboe@kernel.dk>
To: colyli@suse.de
Cc: linux-bcache@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH 0/4] bcache: more fixes for v5.8-rc1
Date: Sun, 14 Jun 2020 16:48:53 -0600 [thread overview]
Message-ID: <595e3582-980e-6cac-66d6-9ced628239e6@kernel.dk> (raw)
In-Reply-To: <20200614165333.124999-1-colyli@suse.de>
On 6/14/20 10:53 AM, colyli@suse.de wrote:
> From: Coly Li <colyli@suse.de>
>
> Hi Jens,
>
> Here are more following up fixes for bcache v5.8-rc1.
>
> The two patches from me are minor clean up. Rested two patches
> are important.
>
> - Mauricio Faria de Oliveira contributes a fix for a potential
> kernel panic when users configures improper block size value
> to bcache backing device. This problem should be fixed as soon
> as possible IMHO.
> - Zhiqiang Liu contributes a fix for a potential deadlock (even quite
> hard to trigger), which I want to have it as soon as possible.
>
> Please take these patches for v5.8-rc1, or -rc2 if it is late for -rc1.
A few hours before -rc1 release is indeed too late. I'd only queue and
push anything this late if there was a very compelling reason to do so.
I've queued them up for -rc2.
--
Jens Axboe
prev parent reply other threads:[~2020-06-14 22:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 16:53 [PATCH 0/4] bcache: more fixes for v5.8-rc1 colyli
2020-06-14 16:53 ` [PATCH 1/4] bcache: fix potential deadlock problem in btree_gc_coalesce colyli
2020-06-14 16:53 ` [PATCH 2/4] bcache: check and adjust logical block size for backing devices colyli
2020-06-14 16:53 ` [PATCH 3/4] bcache: use delayed kworker fo asynchronous devices registration colyli
2020-06-15 6:12 ` Hannes Reinecke
2020-06-14 16:53 ` [PATCH 4/4] bcache: pr_info() format clean up in bcache_device_init() colyli
2020-06-14 22:48 ` 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=595e3582-980e-6cac-66d6-9ced628239e6@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.