From: Marco Rebhan <me@dblsaiko.net>
To: Coly Li <colyli@suse.de>
Cc: linux-bcache@vger.kernel.org, victor@westerhu.is
Subject: Re: Kernel Oops: kernel BUG at block/bio.c:52
Date: Thu, 06 May 2021 17:46:07 +0200 [thread overview]
Message-ID: <2209740.ElGaqSPkdT@invader> (raw)
In-Reply-To: <4b6c9608-84e9-e20b-ac84-c4fd0a536f29@suse.de>
[-- Attachment #1: Type: text/plain, Size: 412 bytes --]
On Thursday, 6 May 2021 12:04:00 CEST Coly Li wrote:
> Before 5.12, the allocation failure returns a NULL pointer, so such
> issue was hidden. I will post a quick fix to emulate previous code
> logic without bothering bio_alloc_bioset().
Ah, I see. I guess that means then I can actually use this patch until
that fix is mainlined :)
> Thanks for the quick test and verification.
Glad to help!
Thanks,
Marco
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-05-06 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 14:54 Kernel Oops: kernel BUG at block/bio.c:52 Victor Westerhuis
2021-04-20 16:14 ` Coly Li
2021-04-27 18:57 ` Marco Rebhan
2021-05-06 2:50 ` Coly Li
2021-05-06 7:36 ` Marco Rebhan
2021-05-06 10:04 ` Coly Li
2021-05-06 15:46 ` Marco Rebhan [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=2209740.ElGaqSPkdT@invader \
--to=me@dblsaiko.net \
--cc=colyli@suse.de \
--cc=linux-bcache@vger.kernel.org \
--cc=victor@westerhu.is \
/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).