linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Charlemagne Lasse <charlemagnelasse@gmail.com>
To: Johannes Weiner <hannes@cmpxchg.org>,
	Michal Hocko <mhocko@kernel.org>,
	 Roman Gushchin <roman.gushchin@linux.dev>,
	Shakeel Butt <shakeel.butt@linux.dev>,
	 Muchun Song <muchun.song@linux.dev>,
	Andrew Morton <akpm@linux-foundation.org>,
	 Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Clark Williams <clrkwllms@kernel.org>,
	 Steven Rostedt <rostedt@goodmis.org>,
	Alexei Starovoitov <ast@kernel.org>,
	 Thomas Gleixner <tglx@linutronix.de>,
	Vlastimil Babka <vbabka@suse.cz>,
	Jakub Kicinski <kuba@kernel.org>,
	 "Peter Zijlstra (Intel)" <peterz@infradead.org>,
	Davidlohr Bueso <dave@stgolabs.net>,
	 LKML <linux-kernel@vger.kernel.org>,
	cgroups@vger.kernel.org, linux-mm@kvack.org,
	 linux-rt-devel@lists.linux.dev
Subject: locking/local_lock, mm: sparse warnings about shadowed variable
Date: Wed, 11 Jun 2025 19:37:10 +0200	[thread overview]
Message-ID: <CAFGhKbwVyxCwYSNrPaQ-GkuP008+uvDg-wNA5syWLLzODCfpcA@mail.gmail.com> (raw)

HI,

when I run `make C=2 mm/mlock.o CHECK="sparse -Wshadow"`, I get a lot of

./include/linux/local_lock.h:88:1: warning: symbol 'l' shadows an earlier one
./include/linux/local_lock.h:88:1: originally declared here

after commit

51339d99c0131bc0d16d378e9b05bc498d2967e2 is the first bad commit
commit 51339d99c0131bc0d16d378e9b05bc498d2967e2
Author: Alexei Starovoitov <ast@kernel.org>
Date:   2025-04-02 19:55:14 -0700

   locking/local_lock, mm: replace localtry_ helpers with local_trylock_t type

   Partially revert commit 0aaddfb06882 ("locking/local_lock: Introduce
   localtry_lock_t").  Remove localtry_*() helpers, since localtry_lock()
   name might be misinterpreted as "try lock".

   Introduce local_trylock[_irqsave]() helpers that only work with newly
   introduced local_trylock_t type.  Note that attempt to use
   local_trylock[_irqsave]() with local_lock_t will cause compilation
   failure.

   Usage and behavior in !PREEMPT_RT:

   local_lock_t lock;                     // sizeof(lock) == 0
   local_lock(&lock);                     // preempt disable
   local_lock_irqsave(&lock, ...);        // irq save
   if (local_trylock_irqsave(&lock, ...)) // compilation error

   local_trylock_t lock;                  // sizeof(lock) == 4
   local_lock(&lock);                     // preempt disable, acquired = 1
   local_lock_irqsave(&lock, ...);        // irq save, acquired = 1
   if (local_trylock(&lock))              // if (!acquired) preempt
disable, acquired = 1
   if (local_trylock_irqsave(&lock, ...)) // if (!acquired) irq save,
acquired = 1

   The existing local_lock_*() macros can be used either with local_lock_t or
   local_trylock_t.  With local_trylock_t they set acquired = 1 while
   local_unlock_*() clears it.

   In !PREEMPT_RT local_lock_irqsave(local_lock_t *) disables interrupts to
   protect critical section, but it doesn't prevent NMI, so the fully
   reentrant code cannot use local_lock_irqsave(local_lock_t *) for exclusive
   access.

   The local_lock_irqsave(local_trylock_t *) helper disables interrupts and
   sets acquired=1, so local_trylock_irqsave(local_trylock_t *) from NMI
   attempting to acquire the same lock will return false.

   In PREEMPT_RT local_lock_irqsave() maps to preemptible spin_lock().  Map
   local_trylock_irqsave() to preemptible spin_trylock().  When in hard IRQ
   or NMI return false right away, since spin_trylock() is not safe due to
   explicit locking in the underneath rt_spin_trylock() implementation.
   Removing this explicit locking and attempting only "trylock" is undesired
   due to PI implications.

   The local_trylock() without _irqsave can be used to avoid the cost of
   disabling/enabling interrupts by only disabling preemption, so
   local_trylock() in an interrupt attempting to acquire the same lock will
   return false.

   Note there is no need to use local_inc for acquired variable, since it's a
   percpu variable with strict nesting scopes.

   Note that guard(local_lock)(&lock) works only for "local_lock_t lock".

   The patch also makes sure that local_lock_release(l) is called before
   WRITE_ONCE(l->acquired, 0).  Though IRQs are disabled at this point the
   local_trylock() from NMI will succeed and local_lock_acquire(l) will warn.

   Link: https://lkml.kernel.org/r/20250403025514.41186-1-alexei.starovoitov@gmail.com
   Fixes: 0aaddfb06882 ("locking/local_lock: Introduce localtry_lock_t")
   Signed-off-by: Alexei Starovoitov <ast@kernel.org>
   Acked-by: Vlastimil Babka <vbabka@suse.cz>
   Acked-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
   Reviewed-by: Shakeel Butt <shakeel.butt@linux.dev>
   Cc: Daniel Borkman <daniel@iogearbox.net>
   Cc: Linus Torvalds <torvalds@linuxfoundation.org>
   Cc: Martin KaFai Lau <martin.lau@kernel.org>
   Cc: Michal Hocko <mhocko@suse.com>
   Cc: Peter Zijlstra <peterz@infradead.org>
   Cc: Steven Rostedt <rostedt@goodmis.org>
   Cc: Vlastimil Babka <vbabka@suse.cz>
   Signed-off-by: Andrew Morton <akpm@linux-foundation.org>

include/linux/local_lock.h          |  58 ++--------
include/linux/local_lock_internal.h | 211 +++++++++++++++---------------------
mm/memcontrol.c                     |  39 ++++---
3 files changed, 116 insertions(+), 192 deletions(-)
bisect found first bad commit


             reply	other threads:[~2025-06-11 17:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11 17:37 Charlemagne Lasse [this message]
2025-06-11 17:57 ` Vlastimil Babka
2025-06-11 18:20   ` Alexei Starovoitov
2025-06-11 22:33     ` Andrew Morton
2025-06-12  7:03     ` Charlemagne Lasse

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=CAFGhKbwVyxCwYSNrPaQ-GkuP008+uvDg-wNA5syWLLzODCfpcA@mail.gmail.com \
    --to=charlemagnelasse@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=ast@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=cgroups@vger.kernel.org \
    --cc=clrkwllms@kernel.org \
    --cc=dave@stgolabs.net \
    --cc=hannes@cmpxchg.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=mhocko@kernel.org \
    --cc=muchun.song@linux.dev \
    --cc=peterz@infradead.org \
    --cc=roman.gushchin@linux.dev \
    --cc=rostedt@goodmis.org \
    --cc=shakeel.butt@linux.dev \
    --cc=tglx@linutronix.de \
    --cc=vbabka@suse.cz \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox