From: Tejun Heo <tj@kernel.org>
To: Waiman Long <longman@redhat.com>
Cc: "Julia Lawall" <Julia.Lawall@inria.fr>,
kernel-janitors@vger.kernel.org,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cgroup: drop unneeded semicolon
Date: Sat, 1 Aug 2026 17:11:52 -1000 [thread overview]
Message-ID: <am61eHsfLMfPCSsE@slm.duckdns.org> (raw)
In-Reply-To: <8797e8b8-59ce-4934-ac0c-7f9731de454b@redhat.com>
Hello,
On Sat, Aug 01, 2026 at 07:37:13PM -0400, Waiman Long wrote:
> > diff --git a/kernel/cgroup/cgroup.c b/kernel/cgroup/cgroup.c
> > index 38f8d9df8..f87fc4550 100644
> > --- a/kernel/cgroup/cgroup.c
> > +++ b/kernel/cgroup/cgroup.c
> > @@ -104,7 +104,7 @@ DEFINE_PERCPU_RWSEM(cgroup_threadgroup_rwsem);
> > #define cgroup_assert_mutex_or_rcu_locked() \
> > RCU_LOCKDEP_WARN(!rcu_read_lock_held() && \
> > !lockdep_is_held(&cgroup_mutex), \
> > - "cgroup_mutex or RCU read lock required");
> > + "cgroup_mutex or RCU read lock required")
> > /*
> > * cgroup destruction makes heavy use of work items and there can be a lot
> >
> The RCU_LOCKDEP_WARN() macro is basically a "do { ...} while (0...)"
> statement. It doesn't have a ';' at the end. So your commit log isn't
> right.
>
> An additional semicolon at the end doesn't harm. By removing the semicolon,
> even if not needed, may make people wonder if it is right when reading the
> code wasting their time to figure out if it is all right. So I don't see any
> advantage in removing it.
I think the extra semicolon can hurt. Imagine something like this:
if (blah)
cgroup_assert_mutex_or_rcu_locked();
else
something else;
This should work but with the extra semicolon, it doesn't. I don't see why
we wouldn't fix this. It's obviously wrong.
Thanks.
--
tejun
next prev parent reply other threads:[~2026-08-02 3:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 19:09 [PATCH] cgroup: drop unneeded semicolon Julia Lawall
2026-08-01 23:37 ` Waiman Long
2026-08-02 3:11 ` Tejun Heo [this message]
2026-08-02 3:31 ` Waiman Long
2026-08-02 6:47 ` Julia Lawall
2026-08-02 19:02 ` Tejun Heo
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=am61eHsfLMfPCSsE@slm.duckdns.org \
--to=tj@kernel.org \
--cc=Julia.Lawall@inria.fr \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mkoutny@suse.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.