From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,minchan@kernel.org,liumartin@google.com,kaleshsingh@google.com,david@redhat.com,richardycc@google.com,akpm@linux-foundation.org
Subject: [merged mm-stable] mm-cma-pairing-the-trace_cma_alloc_start-finish.patch removed from -mm tree
Date: Wed, 09 Jul 2025 22:43:48 -0700 [thread overview]
Message-ID: <20250710054348.CE41FC4CEE3@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/cma: pair the trace_cma_alloc_start/finish
has been removed from the -mm tree. Its filename was
mm-cma-pairing-the-trace_cma_alloc_start-finish.patch
This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Richard Chang <richardycc@google.com>
Subject: mm/cma: pair the trace_cma_alloc_start/finish
Date: Thu, 5 Jun 2025 07:25:32 +0000
In the bad input validation cases, there is no trace_cma_alloc_finish to
match the trace_cma_alloc_start. Move the trace_cma_alloc_start event
after the validations.
Link: https://lkml.kernel.org/r/20250605072532.972081-1-richardycc@google.com
Signed-off-by: Richard Chang <richardycc@google.com>
Acked-by: David Hildenbrand <david@redhat.com>
Cc: Kalesh Singh <kaleshsingh@google.com>
Cc: Martin Liu <liumartin@google.com>
Cc: Minchan Kim <minchan@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/cma.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/mm/cma.c~mm-cma-pairing-the-trace_cma_alloc_start-finish
+++ a/mm/cma.c
@@ -854,8 +854,6 @@ static struct page *__cma_alloc(struct c
unsigned long i;
const char *name = cma ? cma->name : NULL;
- trace_cma_alloc_start(name, count, align);
-
if (!cma || !cma->count)
return page;
@@ -865,6 +863,8 @@ static struct page *__cma_alloc(struct c
if (!count)
return page;
+ trace_cma_alloc_start(name, count, align);
+
for (r = 0; r < cma->nranges; r++) {
page = NULL;
_
Patches currently in -mm which might be from richardycc@google.com are
reply other threads:[~2025-07-10 5:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250710054348.CE41FC4CEE3@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=kaleshsingh@google.com \
--cc=liumartin@google.com \
--cc=minchan@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=richardycc@google.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.