From: "Eric W. Biederman" <ebiederm@xmission.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, kirill.shutemov@linux.intel.com,
jxgao@google.com, dave.hansen@linux.intel.com, bhe@redhat.com,
Ashish.Kalra@amd.com, yan.y.zhao@intel.com
Subject: Re: [merged mm-nonmm-stable] kexec_core-accept-unaccepted-kexec-segments-destination-addresses.patch removed from -mm tree
Date: Mon, 17 Mar 2025 08:33:32 -0500 [thread overview]
Message-ID: <871puv93yr.fsf@email.froward.int.ebiederm.org> (raw)
In-Reply-To: <20250317053306.59F9CC4CEEC@smtp.kernel.org> (Andrew Morton's message of "Sun, 16 Mar 2025 22:33:05 -0700")
Andrew Morton <akpm@linux-foundation.org> writes:
> The quilt patch titled
> Subject: kexec_core: accept unaccepted kexec segments' destination addresses
> has been removed from the -mm tree. Its filename was
> kexec_core-accept-unaccepted-kexec-segments-destination-addresses.patch
>
> This patch was dropped because it was merged into the mm-nonmm-stable branch
> of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
>
The patch is and was broken.
My last comments were completely ignored. Since this was posted
after my comments I had assumed they would be addressed. Since this is
not and never has been a bug fix I assumed that nothing would happen
with this until the merge window and I had a little more time to compose
cohesive response.
All of memory must be accepted before kexec happens because nothing is
done to transfer the state of which pages are accepted and which pages
are not accepted.
The kernel that is kexec'd can't know which pages to accept. If
anything is left unaccepted "Boom" if it tries to accept the wrong
thing then maybe "Boom"
Please revert this broken code.
Eric
next prev parent reply other threads:[~2025-03-17 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 5:33 [merged mm-nonmm-stable] kexec_core-accept-unaccepted-kexec-segments-destination-addresses.patch removed from -mm tree Andrew Morton
2025-03-17 13:33 ` Eric W. Biederman [this message]
2025-03-17 13:43 ` Kirill A. Shutemov
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=871puv93yr.fsf@email.froward.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=Ashish.Kalra@amd.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=dave.hansen@linux.intel.com \
--cc=jxgao@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=mm-commits@vger.kernel.org \
--cc=yan.y.zhao@intel.com \
/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.