mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Song Chen <chensong_2000@189.cn>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org, xiehuan09@gmail.com
Subject: Re: [PATCH] trace/kprobe: remove duplicated call of ring_buffer_event_data
Date: Wed, 19 Oct 2022 09:27:05 +0800	[thread overview]
Message-ID: <19306ab7-6fda-e995-e61d-2ddf4910e126@189.cn> (raw)
In-Reply-To: <20221019002243.8729040161290e17c6581e84@kernel.org>

Hi,

在 2022/10/18 23:22, Masami Hiramatsu (Google) 写道:
> Hi,
> 
> On Tue, 18 Oct 2022 09:59:32 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
> 
>>
>> [ Added Masami who's the new co-maintainer, and this is his code ]
>>
>> On Tue, 18 Oct 2022 15:13:06 +0800
>> Song Chen <chensong_2000@189.cn> wrote:
>>
>>> Function __kprobe_trace_func calls ring_buffer_event_data to get
>>> a ring buffer, however, it has been done in above call
>>> trace_event_buffer_reserve.
>>>
>>> So remove one of them.
>>>
>>
>> May as well add:
>>
>> Fixes: 5e6cd84e2f8bd ("tracing/kprobes: Do not open code event reserve logic")
>>
>> Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> 
> Oops, and we have another line in __kretprobe_trace_func() too.
> 
> Song, can you update this patch to fix the __kretprobe_trace_func() too?
> 
> Thank you,
> 

will do

Song
>>
>> -- Steve
>>
>>
>>> Signed-off-by: Song Chen <chensong_2000@189.cn>
>>> ---
>>>   kernel/trace/trace_kprobe.c | 1 -
>>>   1 file changed, 1 deletion(-)
>>>
>>> diff --git a/kernel/trace/trace_kprobe.c b/kernel/trace/trace_kprobe.c
>>> index 23f7f0ec4f4c..dfd5809a4a65 100644
>>> --- a/kernel/trace/trace_kprobe.c
>>> +++ b/kernel/trace/trace_kprobe.c
>>> @@ -1394,7 +1394,6 @@ __kprobe_trace_func(struct trace_kprobe *tk, struct pt_regs *regs,
>>>   		return;
>>>   
>>>   	fbuffer.regs = regs;
>>> -	entry = fbuffer.entry = ring_buffer_event_data(fbuffer.event);
>>>   	entry->ip = (unsigned long)tk->rp.kp.addr;
>>>   	store_trace_args(&entry[1], &tk->tp, regs, sizeof(*entry), dsize);
>>>   
>>
> 
> 

      reply	other threads:[~2022-10-19  1:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18  7:13 Song Chen
2022-10-18 13:59 ` Steven Rostedt
2022-10-18 15:22   ` Masami Hiramatsu
2022-10-19  1:27     ` Song Chen [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=19306ab7-6fda-e995-e61d-2ddf4910e126@189.cn \
    --to=chensong_2000@189.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=xiehuan09@gmail.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®