mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Long Wei <longwei27@huawei.com>
To: <rppt@kernel.org>, <pasha.tatashin@soleen.com>,
	<pratyush@kernel.org>, <akpm@linux-foundation.org>
Cc: <graf@amazon.com>, <leitao@debian.org>, <corbet@lwn.net>,
	<rdunlap@infradead.org>, <linux-mm@kvack.org>,
	<kexec@lists.infradead.org>, <linux-doc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <hewenliang4@huawei.com>,
	Long Wei <longwei27@huawei.com>
Subject: [PATCH v2 0/2] kho: drop the incoming sub-blob debugfs view
Date: Thu, 19 Nov 2026 14:37:58 +0800	[thread overview]
Message-ID: <20261119063800.698863-1-longwei27@huawei.com> (raw)
In-Reply-To: <20261117092951.4017931-1-longwei27@huawei.com>

kho/in/sub_fdts exposes the raw contents of the sub-blobs described by
the incoming KHO FDT.  KHO does not own those pages: they belong to the
producers' consumers and have independent lifetimes.  LUO, for example,
restores and frees its state in early_initcall, before kho_init()
(fs_initcall) creates the debugfs view, so the blobs point at pages that
are already back in the buddy allocator.  Reading them triggers a KASAN
use-after-free in _copy_to_user().

The same information is already available to user space from in/fdt,
which KHO does own and which stays reserved.  Drop the directory rather
than adding another interface to describe it, keeping the -rc fix small.

Patch 1 removes the interface, patch 2 drops its documentation.

Changes in v2:
- Drop the in/blobs metadata file entirely
- Just remove in/sub_fdts to fix the UAF, no replacement interface
- Update Fixes tag to c609c144b0e8 (the commit that first added sub_fdts)
- Remove the now-unused #include <linux/io.h>

Long Wei (2):
  kho: do not expose incoming sub-blob contents in debugfs
  docs: kho: drop kho/in/sub_fdts description

 Documentation/admin-guide/mm/kho.rst       |  4 --
 kernel/liveupdate/kexec_handover_debugfs.c | 47 +---------------------
 2 files changed, 2 insertions(+), 49 deletions(-)

-- 
2.43.0


  parent reply	other threads:[~2026-11-19  6:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17  9:29 [PATCH 0/2] kho: expose incoming sub-blob metadata instead of contents Long Wei
2026-11-17  9:29 ` [PATCH 1/2] " Long Wei
2026-11-18 16:38   ` Pasha Tatashin
2026-11-17  9:29 ` [PATCH 2/2] docs: kho: describe the in/blobs debugfs file Long Wei
2026-11-19  6:37 ` Long Wei [this message]
2026-11-19  6:37   ` [PATCH v2 1/2] kho: do not expose incoming sub-blob contents in debugfs Long Wei
2026-11-19  8:26     ` Mike Rapoport
2026-11-19  6:38   ` [PATCH v2 2/2] docs: kho: drop kho/in/sub_fdts description Long Wei
2026-11-19  6:53   ` [PATCH v2 0/2] kho: drop the incoming sub-blob debugfs view Pasha Tatashin
2026-11-19  8:26   ` Mike Rapoport

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=20261119063800.698863-1-longwei27@huawei.com \
    --to=longwei27@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=graf@amazon.com \
    --cc=hewenliang4@huawei.com \
    --cc=kexec@lists.infradead.org \
    --cc=leitao@debian.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=pratyush@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=rppt@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

all inboxes | Powered by JetHome®