Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20230526150549.250372621@infradead.org> <20230526151947.027972233@infradead.org>
 <2023052626-blunderer-delegator-4b82@gregkh> <d806769b-c568-fa7c-f7aa-ded9ffea11b4@efficios.com>
 <202305261006.01B34DB4C@keescook>
In-Reply-To: <202305261006.01B34DB4C@keescook>
From:   Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Date:   Fri, 26 May 2023 19:41:04 +0200
Message-ID: <CANiq72=SBvK6cON3s_rdSpsOgUAzZPT+iQeH_fmvatPcKP7fCw@mail.gmail.com>
Subject: Re: [RFC][PATCH 2/2] sched: Use fancy new guards
To:     Kees Cook <keescook@chromium.org>
Cc:     Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
        Greg KH <gregkh@linuxfoundation.org>,
        Peter Zijlstra <peterz@infradead.org>,
        torvalds@linux-foundation.org, pbonzini@redhat.com,
        linux-kernel@vger.kernel.org, ojeda@kernel.org,
        ndesaulniers@google.com, mingo@redhat.com, will@kernel.org,
        longman@redhat.com, boqun.feng@gmail.com, juri.lelli@redhat.com,
        vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
        rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
        bristot@redhat.com, vschneid@redhat.com, paulmck@kernel.org,
        frederic@kernel.org, quic_neeraju@quicinc.com,
        joel@joelfernandes.org, josh@joshtriplett.org,
        jiangshanlai@gmail.com, qiang1.zhang@intel.com,
        rcu@vger.kernel.org, tj@kernel.org, tglx@linutronix.de
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Fri, May 26, 2023 at 7:08=E2=80=AFPM Kees Cook <keescook@chromium.org> w=
rote:
>
> > FWIW C++ has std::scoped_lock. So perhaps using a similar wording may h=
elp ?
>
> Yeah, I like "scoped_*" and "guarded_*" for naming. IMO, it reads better.

FWIW in the Rust side we called the general facility `ScopeGuard`,
then we also have lock `Guard`s and Rust stdlib has things like
`MutexGuard`.

Cheers,
Miguel