From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,hughd@google.com,baolin.wang@linux.alibaba.com,kasong@tencent.com,akpm@linux-foundation.org
Subject: [merged mm-stable] mm-shmem-remove-unnecessary-restrain-unmask-of-swap-gfp-flags.patch removed from -mm tree
Date: Tue, 24 Mar 2026 14:42:45 -0700 [thread overview]
Message-ID: <20260324214246.437CEC19424@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/shmem: remove unnecessary restrain unmask of swap gfp flags
has been removed from the -mm tree. Its filename was
mm-shmem-remove-unnecessary-restrain-unmask-of-swap-gfp-flags.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: Kairui Song <kasong@tencent.com>
Subject: mm/shmem: remove unnecessary restrain unmask of swap gfp flags
Date: Wed, 11 Feb 2026 22:33:23 +0800
The comment makes it look like copy-paste leftovers from
shmem_replace_folio. The first try of the swap doesn't always have a
limited zone.
So don't drop the restraint, which should make the GFP more accurate.
Link: https://lkml.kernel.org/r/20260211-shmem-swap-gfp-v1-1-e9781099a861@tencent.com
Signed-off-by: Kairui Song <kasong@tencent.com>
Reviewed-by: Baolin Wang <baolin.wang@linux.alibaba.com>
Cc: Hugh Dickins <hughd@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/shmem.c | 8 +-------
1 file changed, 1 insertion(+), 7 deletions(-)
--- a/mm/shmem.c~mm-shmem-remove-unnecessary-restrain-unmask-of-swap-gfp-flags
+++ a/mm/shmem.c
@@ -2044,14 +2044,8 @@ static struct folio *shmem_swap_alloc_fo
struct shmem_inode_info *info = SHMEM_I(inode);
struct folio *new, *swapcache;
int nr_pages = 1 << order;
- gfp_t alloc_gfp;
+ gfp_t alloc_gfp = gfp;
- /*
- * We have arrived here because our zones are constrained, so don't
- * limit chance of success with further cpuset and node constraints.
- */
- gfp &= ~GFP_CONSTRAINT_MASK;
- alloc_gfp = gfp;
if (!IS_ENABLED(CONFIG_TRANSPARENT_HUGEPAGE)) {
if (WARN_ON_ONCE(order))
return ERR_PTR(-EINVAL);
_
Patches currently in -mm which might be from kasong@tencent.com are
reply other threads:[~2026-03-24 21:42 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=20260324214246.437CEC19424@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=hughd@google.com \
--cc=kasong@tencent.com \
--cc=mm-commits@vger.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 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.