linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Alexei Starovoitov <ast@fb.com>
Cc: davem@davemloft.net, daniel@iogearbox.net,
	torvalds@linux-foundation.org, peterz@infradead.org,
	netdev@vger.kernel.org, kernel-team@fb.com,
	linux-api@vger.kernel.org
Subject: Re: [PATCH v5 bpf-next 06/10] tracepoint: compute num_args at build time
Date: Mon, 26 Mar 2018 11:56:15 -0400	[thread overview]
Message-ID: <20180326115615.0ca53410@gandalf.local.home> (raw)
In-Reply-To: <20180324023038.938665-7-ast@fb.com>

On Fri, 23 Mar 2018 19:30:34 -0700
Alexei Starovoitov <ast@fb.com> wrote:

> +static void *for_each_tracepoint_range(struct tracepoint * const *begin,
> +				       struct tracepoint * const *end,
> +				       void *(*fct)(struct tracepoint *tp, void *priv),
> +				       void *priv)
>  {
>  	struct tracepoint * const *iter;
> +	void *ret;
>  
>  	if (!begin)
> -		return;
> -	for (iter = begin; iter < end; iter++)
> -		fct(*iter, priv);
> +		return NULL;
> +	for (iter = begin; iter < end; iter++) {
> +		ret = fct(*iter, priv);
> +		if (ret)
> +			return ret;

So you just stopped the loop here. You have an inconsistent state. What
about the functions that were called before. How do you undo them? Or
what about the rest that haven't been touched. This function gives no
feedback to the caller.

-- Steve


> +	}
> +	return NULL;
>  }

  parent reply	other threads:[~2018-03-26 15:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180324023038.938665-1-ast@fb.com>
2018-03-26  8:28 ` [PATCH v5 bpf-next 00/10] bpf, tracing: introduce bpf raw tracepoints Daniel Borkmann
2018-03-26 15:04   ` Steven Rostedt
2018-03-26 15:32     ` Daniel Borkmann
2018-03-26 15:47       ` Steven Rostedt
2018-03-26 16:00         ` Alexei Starovoitov
2018-03-26 16:16           ` Steven Rostedt
     [not found] ` <20180324023038.938665-7-ast@fb.com>
2018-03-26 15:02   ` [PATCH v5 bpf-next 06/10] tracepoint: compute num_args at build time Steven Rostedt
2018-03-26 15:14     ` Mathieu Desnoyers
2018-03-26 15:42       ` Alexei Starovoitov
2018-03-26 15:55         ` Mathieu Desnoyers
2018-03-26 16:08           ` Alexei Starovoitov
2018-03-26 16:17             ` Mathieu Desnoyers
2018-03-26 16:25               ` Alexei Starovoitov
2018-03-26 16:35                 ` Steven Rostedt
2018-03-26 16:47                   ` Alexei Starovoitov
2018-03-26 17:04                     ` Steven Rostedt
2018-03-26 16:57                   ` Mathieu Desnoyers
2018-03-26 17:55                     ` Alexei Starovoitov
2018-03-26 18:11                       ` Steven Rostedt
2018-03-26 18:39                         ` Alexei Starovoitov
2018-03-26 18:48                           ` Steven Rostedt
2018-03-26 21:27                       ` Mathieu Desnoyers
2018-03-26 15:56   ` Steven Rostedt [this message]
2018-03-26 16:31     ` Steven Rostedt

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=20180326115615.0ca53410@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=ast@fb.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=kernel-team@fb.com \
    --cc=linux-api@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).