From: Steven Rostedt <rostedt@goodmis.org>
To: Huang Ying <ying.huang@intel.com>
Cc: "srostedt@redhat.com" <srostedt@redhat.com>,
Shaohua Li <shaohua.li@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [BUGFIX] trace, fix ring_buffer_read_page reading out of page boundary
Date: Fri, 06 Aug 2010 12:50:57 -0400 [thread overview]
Message-ID: <1281113457.3352.3.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1280297641.2771.307.camel@yhuang-dev>
Hi Huang,
Sorry for the late reply, I just got back from vacation. Note, it is
best to send to my goodmis account since I do not always check my RH
email. But ironically, I'm going through my RH email first, so I got
this first ;-)
On Wed, 2010-07-28 at 14:14 +0800, Huang Ying wrote:
> With the configuration: CONFIG_DEBUG_PAGEALLOC=y and Shaohua's patch:
>
> [PATCH]x86: make spurious_fault check correct pte bit
>
> Function call graph trace as follow will trigger page fault.
>
> # cd /sys/kernel/debug/tracing/
> # echo function_graph > current_tracer
> # cat per_cpu/cpu1/trace_pipe_raw > /dev/null
Yep! I can trigger it too. I'll pull in your patch, test it and send it
out for 2.6.36 and stable.
Thanks!
-- Steve
>
> BUG: unable to handle kernel paging request at ffff880006e99000
> IP: [<ffffffff81085572>] rb_event_length+0x1/0x3f
> PGD 1b19063 PUD 1b1d063 PMD 3f067 PTE 6e99160
> Oops: 0000 [#1] SMP DEBUG_PAGEALLOC
> last sysfs file: /sys/devices/virtual/net/lo/operstate
> CPU 1
> Modules linked in:
next prev parent reply other threads:[~2010-08-06 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 6:14 [BUGFIX] trace, fix ring_buffer_read_page reading out of page boundary Huang Ying
2010-08-06 16:50 ` Steven Rostedt [this message]
2010-08-16 17:31 ` [tip:perf/urgent] tracing: Fix " tip-bot for Huang Ying
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=1281113457.3352.3.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=srostedt@redhat.com \
--cc=ying.huang@intel.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