Re: why don't unlock_buffer call directly clear_and_wake_up_bit?

On Tue, May 19, 2026 at 07:42:39PM -0300, Agatha Isabelle Moreira wrote:
> Judging from the commit message at `8236b0ae31c83` I would make the
> educated guess that they are semantically identical, but I don't have
> enough knowledge to make such a claim firmly.
> 
> Maybe the semantics is the same, order doesn't matter and everyone just
> missed it. But maybe nobody changed because order changes semantics, I
> don't know.

Ohhh, I looked at the source right after sending.

The semantics is definetely the same because that's what
`clear_and_wake_up_bit()` does, literally. So yeah, the reason is 100%
sure: the function didn't exist when `unlock_buffer()` was written.


---
Sincerely,
Agatha Isabelle Moreira
C Developer | agatha.dev
Sourcehut: https://sr.ht/~devlavender/