From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, vincenzo.frascino@arm.com,
urezki@gmail.com, ryabinin.a.a@gmail.com, glider@google.com,
dvyukov@google.com, david@redhat.com, andreyknvl@gmail.com,
hch@lst.de, akpm@linux-foundation.org
Subject: [merged mm-stable] mm-call-vfree-instead-of-__vunmap-from-delayed_vfree_work.patch removed from -mm tree
Date: Thu, 02 Feb 2023 22:38:34 -0800 [thread overview]
Message-ID: <20230203063834.DD3A6C433EF@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm: call vfree instead of __vunmap from delayed_vfree_work
has been removed from the -mm tree. Its filename was
mm-call-vfree-instead-of-__vunmap-from-delayed_vfree_work.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: Christoph Hellwig <hch@lst.de>
Subject: mm: call vfree instead of __vunmap from delayed_vfree_work
Date: Sat, 21 Jan 2023 08:10:46 +0100
This adds an extra, never taken, in_interrupt() branch, but will allow to
cut down the maze of vfree helpers.
Link: https://lkml.kernel.org/r/20230121071051.1143058-6-hch@lst.de
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
Cc: Alexander Potapenko <glider@google.com>
Cc: Andrey Konovalov <andreyknvl@gmail.com>
Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
Cc: Dmitry Vyukov <dvyukov@google.com>
Cc: Vincenzo Frascino <vincenzo.frascino@arm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
--- a/mm/vmalloc.c~mm-call-vfree-instead-of-__vunmap-from-delayed_vfree_work
+++ a/mm/vmalloc.c
@@ -2707,7 +2707,7 @@ static void delayed_vfree_work(struct wo
struct llist_node *t, *llnode;
llist_for_each_safe(llnode, t, llist_del_all(&p->list))
- __vunmap((void *)llnode, 1);
+ vfree(llnode);
}
/**
_
Patches currently in -mm which might be from hch@lst.de are
reply other threads:[~2023-02-03 6:44 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=20230203063834.DD3A6C433EF@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=david@redhat.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=ryabinin.a.a@gmail.com \
--cc=urezki@gmail.com \
--cc=vincenzo.frascino@arm.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.