mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: walimis <walimisdev@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] ftrace: fix wrong pos computing when read buffer has been fulfilled.
Date: Tue, 18 Nov 2008 23:17:21 +0800	[thread overview]
Message-ID: <20081118151721.GA23383@ubuntu.mshome.net> (raw)
In-Reply-To: <alpine.DEB.1.10.0811180933490.15003@gandalf.stny.rr.com>

On Tue, Nov 18, 2008 at 09:36:07AM -0500, Steven Rostedt wrote:
>
>On Sat, 15 Nov 2008, walimis wrote:
>
>> 
>> hi Steven,
>> 
>> Could you help me to review this patch?
>> 
>> Thanks.
>> 
>> Impact: make output of available_filter_functions complete
>> 
>> phenomenon:
>> 
>> The first value of dyn_ftrace_total_info is not equal with
>> `cat available_filter_functions | wc -l`, but they should be equal.
>> 
>> root cause:
>> 
>> When printing functions with seq_printf in t_show, if the read buffer
>> is just overflowed by current function record, then this function
>> won't be printed to user space through read buffer, it will
>> just be dropped. So we can't see this function printing.
>> So, every time the last function to fill the read buffer, if overflowed,
>> will be dropped.
>> This also applies to set_ftrace_filter if set_ftrace_filter has
>> more bytes than read buffer.
>> 
>> fix:
>> 
>> Through checking return value of seq_printf, if less than 0, we know
>> this function doesn't be printed. Then we decrease position to force
>> this function to be printed next time, in next read buffer.
>
>A lot of the code for seq files I cut and paste from other places that I 
>have written it. The seq files always confuse me, so I like to use stuff 
>that worked before. Some of the things that walimis fixed were not needed 
>for this file, and was overkill.
It also confuse me a lot. I also checked all places using seq files in
trace/ftrace code, to see whether there are similar problem.
  - trace.c: in s_start() it force pos to decrease one such as: 
	l = *pos - 1;
	so it works well.
  - trace_stack.c: t_start, in almost all cases, can be only called
    once, so we don't see the error. But I wonder whether it still works
    well if output message exceeds the size of seq file buffer and call
    t_start twice. If needed, I can test it.
  - trace_branch.c : the same with above.


walimis
>
>> 
>> another little fix is to show correct allocating pages count.
>
>Ack.
>
>> 
>> Signed-off-by: walimis <walimisdev@gmail.com>
>
>Acked-by: Steven Rostedt <srostedt@redhat.com>
>
>-- Steve

  reply	other threads:[~2008-11-18 15:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-15  7:19 walimis
2008-11-16  7:33 ` Ingo Molnar
2008-11-16 15:01   ` Steven Rostedt
2008-11-16 16:06     ` walimis
2008-11-18 14:36 ` Steven Rostedt
2008-11-18 15:17   ` walimis [this message]
2008-11-18 15:31     ` Steven Rostedt
2008-11-18 15:52       ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2008-11-14 17:40 walimis

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=20081118151721.GA23383@ubuntu.mshome.net \
    --to=walimisdev@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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®