mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH] ring-buffer: Remove jump to out label in ring_buffer_swap_cpu()
Date: Wed, 28 May 2025 09:32:17 +0900	[thread overview]
Message-ID: <20250528093217.5a106d3561b2234080e3be35@kernel.org> (raw)
In-Reply-To: <20250527145753.6b45d840@gandalf.local.home>

On Tue, 27 May 2025 14:57:53 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:

> From: Steven Rostedt <rostedt@goodmis.org>
> 
> The function ring_buffer_swap_cpu() has a bunch of jumps to the label out
> that simply returns "ret". There's no reason to jump to a label that
> simply returns a value. Just return directly from there.
> 
> This goes back to almost the beginning when commit 8aabee573dff
> ("ring-buffer: remove unneeded get_online_cpus") was introduced. That
> commit removed a put_online_cpus() from that label, but never updated all
> the jumps to it that now no longer needed to do anything but return a
> value.
> 

Looks good to me.

Reviewed-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>

> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> ---
>  kernel/trace/ring_buffer.c | 23 +++++++++--------------
>  1 file changed, 9 insertions(+), 14 deletions(-)
> 
> diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
> index 897ce51d3bbf..e2aa90dc8d9e 100644
> --- a/kernel/trace/ring_buffer.c
> +++ b/kernel/trace/ring_buffer.c
> @@ -6309,37 +6309,33 @@ int ring_buffer_swap_cpu(struct trace_buffer *buffer_a,
>  
>  	if (!cpumask_test_cpu(cpu, buffer_a->cpumask) ||
>  	    !cpumask_test_cpu(cpu, buffer_b->cpumask))
> -		goto out;
> +		return -EINVAL;
>  
>  	cpu_buffer_a = buffer_a->buffers[cpu];
>  	cpu_buffer_b = buffer_b->buffers[cpu];
>  
>  	/* It's up to the callers to not try to swap mapped buffers */
> -	if (WARN_ON_ONCE(cpu_buffer_a->mapped || cpu_buffer_b->mapped)) {
> -		ret = -EBUSY;
> -		goto out;
> -	}
> +	if (WARN_ON_ONCE(cpu_buffer_a->mapped || cpu_buffer_b->mapped))
> +		return -EBUSY;
>  
>  	/* At least make sure the two buffers are somewhat the same */
>  	if (cpu_buffer_a->nr_pages != cpu_buffer_b->nr_pages)
> -		goto out;
> +		return -EINVAL;
>  
>  	if (buffer_a->subbuf_order != buffer_b->subbuf_order)
> -		goto out;
> -
> -	ret = -EAGAIN;
> +		return -EINVAL;
>  
>  	if (atomic_read(&buffer_a->record_disabled))
> -		goto out;
> +		return -EAGAIN;
>  
>  	if (atomic_read(&buffer_b->record_disabled))
> -		goto out;
> +		return -EAGAIN;
>  
>  	if (atomic_read(&cpu_buffer_a->record_disabled))
> -		goto out;
> +		return -EAGAIN;
>  
>  	if (atomic_read(&cpu_buffer_b->record_disabled))
> -		goto out;
> +		return -EAGAIN;
>  
>  	/*
>  	 * We can't do a synchronize_rcu here because this
> @@ -6376,7 +6372,6 @@ int ring_buffer_swap_cpu(struct trace_buffer *buffer_a,
>  out_dec:
>  	atomic_dec(&cpu_buffer_a->record_disabled);
>  	atomic_dec(&cpu_buffer_b->record_disabled);
> -out:
>  	return ret;
>  }
>  EXPORT_SYMBOL_GPL(ring_buffer_swap_cpu);
> -- 
> 2.47.2
> 


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

      reply	other threads:[~2025-05-28  0:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-27 18:57 Steven Rostedt
2025-05-28  0:32 ` Masami Hiramatsu [this message]

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=20250528093217.5a106d3561b2234080e3be35@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=rostedt@goodmis.org \
    /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®