From: kernel test robot <lkp@intel.com>
To: Suren Baghdasaryan <surenb@google.com>
Cc: oe-kbuild-all@lists.linux.dev,
David Hildenbrand <david@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
mm-commits@vger.kernel.org,
"Liam R. Howlett (Oracle)" <liam@infradead.org>,
"Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Subject: [akpm-mm:mm-new 439/459] fs/proc/task_mmu.c:205:13: warning: 'reacquire_rcu' defined but not used
Date: Sat, 12 Sep 2026 14:39:55 +0200 [thread overview]
Message-ID: <202609121422.hkKWuy7K-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-new
head: 383fc05d4650b021f3c17e36a145106dcc61a294
commit: 2a61a4b80dc01581dc9f6935eedefbd596e77409 [439/459] proc/task_mmu: remove unnecessary inlines in function definitions
config: openrisc-randconfig-r053-20260912 (https://download.01.org/0day-ci/archive/20260912/202609121422.hkKWuy7K-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260912/202609121422.hkKWuy7K-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202609121422.hkKWuy7K-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/proc/task_mmu.c:205:13: warning: 'reacquire_rcu' defined but not used [-Wunused-function]
205 | static void reacquire_rcu(struct proc_maps_private *priv)
| ^~~~~~~~~~~~~
>> fs/proc/task_mmu.c:197:13: warning: 'drop_rcu' defined but not used [-Wunused-function]
197 | static void drop_rcu(struct proc_maps_private *priv)
| ^~~~~~~~
fs/proc/task_mmu.c:133:12: warning: 'lock_ctx_mm' defined but not used [-Wunused-function]
133 | static int lock_ctx_mm(struct proc_maps_locking_ctx *lock_ctx)
| ^~~~~~~~~~~
vim +/reacquire_rcu +205 fs/proc/task_mmu.c
196
> 197 static void drop_rcu(struct proc_maps_private *priv)
198 {
199 if (priv->lock_ctx.mmap_locked)
200 return;
201
202 rcu_read_unlock();
203 }
204
> 205 static void reacquire_rcu(struct proc_maps_private *priv)
206 {
207 if (priv->lock_ctx.mmap_locked)
208 return;
209
210 rcu_read_lock();
211 /* Reinitialize the iterator. */
212 vma_iter_set(&priv->iter, priv->lock_ctx.locked_vma->vm_end);
213 }
214
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-09-12 12:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 12:39 kernel test robot [this message]
2026-09-14 15:01 ` [akpm-mm:mm-new 439/459] fs/proc/task_mmu.c:205:13: warning: 'reacquire_rcu' defined but not used Suren Baghdasaryan
2026-09-14 19:09 ` Suren Baghdasaryan
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=202609121422.hkKWuy7K-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=liam@infradead.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--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.