From: "Jackie Liu" <liu.yun@linux.dev>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: glider@google.com, dvyukov@google.com, elver@google.com,
pjw@kernel.org, alex@ghiti.fr, aou@eecs.berkeley.edu,
linux-riscv@lists.infradead.org, linux-mm@kvack.org,
kasan-dev@googlegroups.com, muchun.song@linux.dev
Subject: Re: [PATCH v2 0/3] kfence: fix pool allocation failure handling
Date: Fri, 30 Oct 2026 05:55:21 +0000 [thread overview]
Message-ID: <67833df2daf24cc413c212c14306b9230dde996f@linux.dev> (raw)
In-Reply-To: <20261029182645.d6e7b119a562c973d19cda63@linux-foundation.org>
2026年10月30日 09:26, "Andrew Morton" <akpm@linux-foundation.org mailto:akpm@linux-foundation.org?to=%22Andrew%20Morton%22%20%3Cakpm%40linux-foundation.org%3E > 写到:
>
> On Thu, 29 Oct 2026 10:57:40 +0800 Jackie Liu <liu.yun@linux.dev> wrote:
>
> >
> > Fix the cleanup address and page reuse window in failed late KFENCE
> > initialization. Also let RISC-V boot if the early pool reservation fails.
> >
> > Patch 2 depends on patch 1. Patch 3 can be applied independently.
> >
> Thanks.
>
> We're all horridly busy with bugfixes at present and the first thing
> recipients think when presented with yet another is "why should I look
> at this".
>
> So it really helps to start out with a succinct and punchy sentence
> which explains that thing.
>
> LLM suggested to me
>
> : KFENCE initialization failures can cause kernel crashes or memory
> : corruption, while a RISC-V failure can prevent the system from booting.
> : These fixes make the failure paths safe and allow systems to continue
> : running with KFENCE disabled.
>
> How does that sound?
Hi Andrew,
Thanks for the suggestion. That wording sounds good to me. It makes
the impact of these bugs much clearer, and I'll keep this in mind
when writing future patch descriptions.
Also, Sashiko has reported an issue with patch 3/3.
Could you please apply only the first two patches and drop patch 3/3
for now? I'll address the reported issue and resend the third patch
separately once it's fixed.
Thanks,
Jackie
>
next prev parent reply other threads:[~2026-10-30 5:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 2:57 [PATCH v2 0/3] kfence: fix pool allocation failure handling Jackie Liu
2026-10-29 2:57 ` [PATCH v2 1/3] kfence: fix pool cleanup on metadata allocation failure Jackie Liu
2026-10-29 2:57 ` [PATCH v2 2/3] kfence: clear the pool pointer before freeing pages Jackie Liu
2026-10-29 2:57 ` [PATCH v2 3/3] riscv: keep booting if KFENCE pool reservation fails Jackie Liu
2026-10-30 2:58 ` sashiko-bot
2026-10-30 1:26 ` [PATCH v2 0/3] kfence: fix pool allocation failure handling Andrew Morton
2026-10-30 5:55 ` Jackie Liu [this message]
2026-10-30 6:55 ` Andrew Morton
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=67833df2daf24cc413c212c14306b9230dde996f@linux.dev \
--to=liu.yun@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=muchun.song@linux.dev \
--cc=pjw@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