linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: Coly Li <colyli@suse.de>
Cc: linux-bcache@vger.kernel.org
Subject: Re: [PATCH v4] bcache: avoid oversized read request in cache missing code path
Date: Wed, 26 May 2021 16:59:48 +0100	[thread overview]
Message-ID: <87tumpiiyz.fsf@esperi.org.uk> (raw)
In-Reply-To: <20210526151450.45211-1-colyli@suse.de> (Coly Li's message of "Wed, 26 May 2021 23:14:50 +0800")

On 26 May 2021, Coly Li said:
> Current problmatic code can be partially found since Linux v5.13-rc1,
> therefore all maintained stable kernels should try to apply this fix.

I thought this crash was observed with 5.12 originally? (I know that's
why I'm still on 5.11 :) )

  reply	other threads:[~2021-05-26 16:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26 15:14 [PATCH v4] bcache: avoid oversized read request in cache missing code path Coly Li
2021-05-26 15:59 ` Nix [this message]
2021-05-27  2:55   ` Coly Li
2021-05-27 11:36 ` Christoph Hellwig

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=87tumpiiyz.fsf@esperi.org.uk \
    --to=nix@esperi.org.uk \
    --cc=colyli@suse.de \
    --cc=linux-bcache@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 NNTP newsgroup(s).