On Mon, Jun 22 2026 at 09:38, Usama Arif wrote:
> __csd_lock_record() publishes per-CPU CSD debug state that is read by
> csd_lock_wait_toolong() on another CPU. The remote side first reads
> cur_csd with smp_load_acquire() and, when non-NULL, may then read the
> matching cur_csd_func and cur_csd_info fields.
That's not how a change log should look like. See
https://docs.kernel.org/process/maintainer-tip.html#changelog
When I use that template of context, problem, solution, then I clearly
have to assume that the above paragraph describes the current state,
which is not the case.
So in the first paragraph you want to explain that the code uses
smp_mb() to protect against foo.
The second paragraph explains the problem, i.e. that smp_mb() is a big
hammer.
The third paragraph explains how this can be replaced and why the
replacement is correct.
