mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Carles Pey <carles.pey@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] ftrace: add unit test for removing trace function
Date: Tue, 7 Sep 2021 21:40:47 -0400	[thread overview]
Message-ID: <20210907214047.04ef5ac8@rorschach.local.home> (raw)
In-Reply-To: <20210904180248.1886220-2-carles.pey@gmail.com>

On Sat,  4 Sep 2021 22:02:48 +0400
Carles Pey <carles.pey@gmail.com> wrote:


Two errors here.

-ENOCHANGELOG
-ENOSIG

No matter how trivial the patch, you need a change log. The subject is
"what" the patch does, the change log is "why" it is done. What was the
motivation for this patch.

And more critical, I can't even take this patch because there's no
"Signed-off-by".

-- Steve


> ---
>  kernel/trace/trace_selftest.c | 34 ++++++++++++++++++++++++++++++++++
>  1 file changed, 34 insertions(+)
> 
> diff --git a/kernel/trace/trace_selftest.c b/kernel/trace/trace_selftest.c
> index adf7ef194005..875b4f1a0476 100644
> --- a/kernel/trace/trace_selftest.c
> +++ b/kernel/trace/trace_selftest.c
> @@ -287,6 +287,40 @@ static int trace_selftest_ops(struct trace_array *tr, int cnt)
>  	if (trace_selftest_test_probe3_cnt != 4)
>  		goto out_free;
>  
> +	/* Remove trace function from probe 3 */
> +	func1_name = "!" __stringify(DYN_FTRACE_TEST_NAME);
> +	len1 = strlen(func1_name);
> +
> +	ftrace_set_filter(&test_probe3, func1_name, len1, 0);
> +
> +	DYN_FTRACE_TEST_NAME();
> +
> +	print_counts();
> +
> +	if (trace_selftest_test_probe1_cnt != 3)
> +		goto out_free;
> +	if (trace_selftest_test_probe2_cnt != 2)
> +		goto out_free;
> +	if (trace_selftest_test_probe3_cnt != 4)
> +		goto out_free;
> +	if (cnt > 1) {
> +		if (trace_selftest_test_global_cnt == 0)
> +			goto out_free;
> +	}
> +	if (trace_selftest_test_dyn_cnt == 0)
> +		goto out_free;
> +
> +	DYN_FTRACE_TEST_NAME2();
> +
> +	print_counts();
> +
> +	if (trace_selftest_test_probe1_cnt != 3)
> +		goto out_free;
> +	if (trace_selftest_test_probe2_cnt != 3)
> +		goto out_free;
> +	if (trace_selftest_test_probe3_cnt != 5)
> +		goto out_free;
> +
>  	ret = 0;
>   out_free:
>  	unregister_ftrace_function(dyn_ops);


      reply	other threads:[~2021-09-08  1:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-04 18:02 [PATCH 0/1] " Carles Pey
2021-09-04 18:02 ` [PATCH 1/1] " Carles Pey
2021-09-08  1:40   ` Steven Rostedt [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=20210907214047.04ef5ac8@rorschach.local.home \
    --to=rostedt@goodmis.org \
    --cc=carles.pey@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    /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®