From: Jens Axboe <axboe@kernel.dk>
To: Coly Li <colyli@suse.de>
Cc: linux-bcache@vger.kernel.org, linux-block@vger.kernel.org,
rolf@rolffokkens.nl, pierre.juhen@orange.fr
Subject: Re: [PATCH 0/2] bcache: two emergent fixes for Linux v5.2-rc5
Date: Thu, 13 Jun 2019 03:09:28 -0600 [thread overview]
Message-ID: <d90c5b6a-f55a-abeb-fa2f-19e3d0e3b42e@kernel.dk> (raw)
In-Reply-To: <20190609221335.24616-1-colyli@suse.de>
On 6/9/19 4:13 PM, Coly Li wrote:
> Hi Jens,
>
> Here are two emergent fixes that we should have in Linux v5.2-rc5.
>
> - bcache: fix stack corruption by PRECEDING_KEY()
> This patch fixes a GCC9 compiled bcache panic problem, which is
> reported by Fedora Core, Arch Linux and SUSE Leap Linux users whose
> kernels are combiled with GCC9. This bug hides for long time since
> v4.13 and triggered by the new GCC9.
> When people upgrade their kernel to a GCC9 compiled kernel, this
> bug may cause the metadata corruption. So we should have this fix
> in upstream ASAP.
>
> - bcache: only set BCACHE_DEV_WB_RUNNING when cached device attached
> There are 2 users report bcache panic after changing writeback
> percentage of an non-attached bcache device. Therefore I suggest
> to have this fix upstream in this run.
>
> Thank you in advance for taking care of these two fixes.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2019-06-13 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 22:13 [PATCH 0/2] bcache: two emergent fixes for Linux v5.2-rc5 Coly Li
2019-06-09 22:13 ` [PATCH 1/2] bcache: fix stack corruption by PRECEDING_KEY() Coly Li
2019-06-09 22:13 ` [PATCH 2/2] bcache: only set BCACHE_DEV_WB_RUNNING when cached device attached Coly Li
2019-06-13 9:09 ` 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=d90c5b6a-f55a-abeb-fa2f-19e3d0e3b42e@kernel.dk \
--to=axboe@kernel.dk \
--cc=colyli@suse.de \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=pierre.juhen@orange.fr \
--cc=rolf@rolffokkens.nl \
/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.