[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210910170937.GM4323@worktop.programming.kicks-ass.net>
Date: Fri, 10 Sep 2021 19:09:37 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Waiman Long <llong@...hat.com>
Cc: Will Deacon <will@...nel.org>, tglx@...utronix.de,
boqun.feng@...il.com, linux-kernel@...r.kernel.org,
Ingo Molnar <mingo@...nel.org>,
Juri Lelli <juri.lelli@...hat.com>,
Steven Rostedt <rostedt@...dmis.org>,
Davidlohr Bueso <dave@...olabs.net>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Mike Galbraith <efault@....de>,
Daniel Bristot de Oliveira <bristot@...hat.com>
Subject: Re: [PATCH 1/4] sched/wakeup: Strengthen
current_save_and_set_rtlock_wait_state()
On Fri, Sep 10, 2021 at 12:07:40PM -0400, Waiman Long wrote:
> > #define set_special_state(state_value) \
> > do { \
> > - unsigned long flags; /* may shadow */ \
> > + unsigned long __flags; /* may shadow */ \
>
> Do you still need the "may shadow" comment?
Strictly speaking yes, there _could_ be a local variable called __flags,
however unlikely.
At some point someone was going around and doing dodgy patches based on
compiler warnings about variables being shadowed, this it to preempt
anybody trying to 'fix' this (again).
Powered by blists - more mailing lists