From: Andrew Morton <akpm@linux-foundation.org>
To: "Jackie Liu" <liu.yun@linux.dev>
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: Thu, 29 Oct 2026 23:55:29 -0700 [thread overview]
Message-ID: <20261029235529.0a4a37da0ae150fcfd4ef954@linux-foundation.org> (raw)
In-Reply-To: <67833df2daf24cc413c212c14306b9230dde996f@linux.dev>
On Fri, 30 Oct 2026 05:55:21 +0000 "Jackie Liu" <liu.yun@linux.dev> wrote:
>
> Also, Sashiko has reported an issue with patch 3/3.
thanks, I missed that.
> 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.
Sure.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: "Jackie Liu" <liu.yun@linux.dev>
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: Thu, 29 Oct 2026 23:55:29 -0700 [thread overview]
Message-ID: <20261029235529.0a4a37da0ae150fcfd4ef954@linux-foundation.org> (raw)
In-Reply-To: <67833df2daf24cc413c212c14306b9230dde996f@linux.dev>
On Fri, 30 Oct 2026 05:55:21 +0000 "Jackie Liu" <liu.yun@linux.dev> wrote:
>
> Also, Sashiko has reported an issue with patch 3/3.
thanks, I missed that.
> 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.
Sure.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-10-30 6:55 UTC|newest]
Thread overview: 15+ 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 ` 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 ` 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 ` Jackie Liu
2026-10-29 2:57 ` [PATCH v2 3/3] riscv: keep booting if KFENCE pool reservation fails Jackie Liu
2026-10-29 2:57 ` 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 1:26 ` Andrew Morton
2026-10-30 5:55 ` Jackie Liu
2026-10-30 5:55 ` Jackie Liu
2026-10-30 6:55 ` Andrew Morton [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=20261029235529.0a4a37da0ae150fcfd4ef954@linux-foundation.org \
--to=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=liu.yun@linux.dev \
--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 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.