From: Sasha Levin <sashal@kernel.org>
To: "Kiryl Shutsemau (Meta)" <kas@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org,
"Mike Rapoport (Microsoft)" <rppt@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Pankaj Gupta <pankaj.gupta@amd.com>,
David Hildenbrand <david@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
Lorenzo Stoakes <ljs@kernel.org>, Michal Hocko <mhocko@suse.com>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@kernel.org>
Subject: Re: [PATCH 6.6.y] mm/cma: accept memory of CMA areas reserved at a fixed address
Date: Wed, 18 Nov 2026 07:40:01 -0500 [thread overview]
Message-ID: <20261118124002.3727477-5-sashal@kernel.org> (raw)
In-Reply-To: <avszpOC2q4p8dVVK@shutemov.name>
On Mon, Nov 16, 2026 at 04:48:52PM +0000, Kiryl Shutsemau (Meta) wrote:
> accept_memory() takes (start, end) in 6.6. It was converted to
> (start, size) in 6.12. See 5adfeaecc487 ("mm: rework accept memory
> helpers"). Here size is taken as the end address. For the usual
> cma=<size>@<base>, base is above size and nothing gets accepted, so the
> bug stays.
The copy in the 6.6 queue is not the one that was posted. It already calls
accept_memory(base, base + size), see
queue-6.6/mm-cma-accept-memory-of-cma-areas-reserved-at-a-fixe.patch and its "[
sashal: ... ]" note.
The 6.12 copy passes (base, size), matching the 6.12 signature, as you say.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-11-18 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 1:12 FAILED: patch "[PATCH] mm/cma: accept memory of CMA areas reserved at a fixed address" failed to apply to 6.6-stable tree Sasha Levin
2026-11-14 16:22 ` [PATCH 6.6.y] mm/cma: accept memory of CMA areas reserved at a fixed address Sasha Levin
2026-11-16 16:48 ` Kiryl Shutsemau (Meta)
2026-11-18 12:40 ` Sasha Levin [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=20261118124002.3727477-5-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=kas@kernel.org \
--cc=liam@infradead.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=pankaj.gupta@amd.com \
--cc=rppt@kernel.org \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=vbabka@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