From: Andrew Morton <akpm@linux-foundation.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: linux-kernel@vger.kernel.org,
Suren Baghdasaryan <surenb@google.com>,
Kent Overstreet <kent.overstreet@linux.dev>,
Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH] lib: Split codetag_lock_module_list()
Date: Tue, 24 Mar 2026 15:12:27 -0700 [thread overview]
Message-ID: <20260324151227.7bd7a52c1403cb4882ab713e@linux-foundation.org> (raw)
In-Reply-To: <20260324214226.3684605-1-bvanassche@acm.org>
On Tue, 24 Mar 2026 14:42:25 -0700 Bart Van Assche <bvanassche@acm.org> wrote:
> Letting a function argument indicate whether a lock or unlock operation
> should be performed is incompatible with compile-time analysis of
> locking operations by sparse and Clang.
And it makes Linus mad.
> Hence, split
> codetag_lock_module_list() into two functions: a function that locks
> cttype->mod_lock and another function that unlocks cttype->mod_lock. No
> functionality has been changed. See also commit 916cc5167cc6 ("lib: code
> tagging framework").
Thanks. I'd prefer to park this for the next cycle. The amount of
material I'm sitting on is excessive and I'm trying to give
reviews&testers time to catch up.
next prev parent reply other threads:[~2026-03-24 22:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 21:42 Bart Van Assche
2026-03-24 22:12 ` Andrew Morton [this message]
2026-03-25 0:26 ` 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=20260324151227.7bd7a52c1403cb4882ab713e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bvanassche@acm.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®