On 2024-12-27 12:19:46 [-0500], Steven Rostedt wrote:
…
> Is easier to understand than:
>
> if (!mod) {
> guard(rcu)();
> mod = __module_text_address(pc);
> }
>
> Because it makes me wonder, why use a guard() for a one liner?
Why not? The context ends immediately after.
> But, when I saw your other patch, if we had:
>
> if (!mod) {
> scoped_guard(rcu)()
> mod = __module_text_address(pc);
> }
Okay, if this looks better, let me update it. It just you already have a
scope (the {} after the if) and then we start yet another block. But if
this looks better so be it.
> To me, hat looks much better than the guard() as it is obvious to what the
> code is protecting. Even though, I still prefer the explicit, lock/unlock.
> Maybe, just because I'm more used to it.
I'm probably also used to the explicit part but numerous people said to
use this from now on. And it results in less lines and you don't have to
worry about each return statement. So it somehow looks/ feels line an
upgrade.
> IMHO, guard() is for complex functions that are error prone. A single line
> is not something that is error prone (unless you don't match the lock and
> unlock properly, but that's pretty obvious when that happens).
True but this is now a one liner which might be extended later on. Also
the context is one line.
> But this is just my own opinion.
>
> -- Steve
Sebastian
