From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,surenb@google.com,akpm@linux-foundation.org
Subject: [to-be-updated] proc-task_mmu-remove-unnecessary-inlines-in-function-definitions-fix.patch removed from -mm tree
Date: Thu, 17 Sep 2026 09:22:54 -0700 [thread overview]
Message-ID: <20260917162254.6FA0A1F00898@smtp.kernel.org> (raw)
The quilt patch titled
Subject: proc-task_mmu-remove-unnecessary-inlines-in-function-definitions-fix
has been removed from the -mm tree. Its filename was
proc-task_mmu-remove-unnecessary-inlines-in-function-definitions-fix.patch
This patch was dropped because an updated version will be issued
------------------------------------------------------
From: Suren Baghdasaryan <surenb@google.com>
Subject: proc-task_mmu-remove-unnecessary-inlines-in-function-definitions-fix
Date: Mon, 14 Sep 2026 12:06:31 -0700
Uninlined drop_rcu() and reacquire_rcu() functions are not used when
CONFIG_PROC_PAGE_MONITOR=n. Exclure them in this configuration.
Link: https://lore.kernel.org/20260914190631.3167420-1-surenb@google.com
Fixes: 7edb437cbbfc ("proc/task_mmu: remove unnecessary inlines in function definitions")
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202609121422.hkKWuy7K-lkp@intel.com/
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
fs/proc/task_mmu.c | 2 ++
1 file changed, 2 insertions(+)
--- a/fs/proc/task_mmu.c~proc-task_mmu-remove-unnecessary-inlines-in-function-definitions-fix
+++ a/fs/proc/task_mmu.c
@@ -194,6 +194,7 @@ static bool fallback_to_mmap_lock(struct
return true;
}
+#ifdef CONFIG_PROC_PAGE_MONITOR
static void drop_rcu(struct proc_maps_private *priv)
{
if (priv->lock_ctx.mmap_locked)
@@ -211,6 +212,7 @@ static void reacquire_rcu(struct proc_ma
/* Reinitialize the iterator. */
vma_iter_set(&priv->iter, priv->lock_ctx.locked_vma->vm_end);
}
+#endif
static struct vm_area_struct *proc_get_vma(struct seq_file *m, loff_t *ppos)
{
_
Patches currently in -mm which might be from surenb@google.com are
proc-task_mmu-clarify-shmem-mapping-walk-conditions-in-smap_gather_stats.patch
proc-task_mmu-remove-special-casing-of-smap_gather_stats-start-parameter.patch
proc-task_mmu-change-proc_get_vma-to-stop-returning-gate-vma-at-the-end.patch
proc-task_mmu-read-proc-pid-smaps_rollup-under-per-vma-lock.patch
selftests-proc-add-proc-pid-smaps_rollup-tearing-tests.patch
reply other threads:[~2026-09-17 16:22 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=20260917162254.6FA0A1F00898@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=mm-commits@vger.kernel.org \
--cc=surenb@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.