From: Srinivasa Ds <srinivasa@in.ibm.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: ananth@in.ibm.com, Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Masami Hiramatsu <mhiramat@redhat.com>,
Jim Keniston <jkenisto@us.ibm.com>
Subject: Re: [RFC] [patch 1/2] add non_init_kernel_text_address
Date: Tue, 01 Jan 2008 12:04:02 +0530 [thread overview]
Message-ID: <4779DEDA.90207@in.ibm.com> (raw)
In-Reply-To: <200712191611.52239.rusty@rustcorp.com.au>
Rusty Russell wrote:
>
> Subject: Don't report discarded init pages as kernel text.
>
> Current code could cause a bug in symbol_put_addr() if an arch used
> kmalloc module text: we might think the symbol belongs to the core
> kernel.
>
> The downside is that this might make backtraces through (discarded)
> init functions harder to read on some archs, but we already have that
> issue for modules and noone has complained.
Thanks Rusty, This patch fixes my problem.
Tested-by: Srinivasa DS <srinivasa@in.ibm.com>
next prev parent reply other threads:[~2008-01-01 7:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 6:55 [RFC] [patch 1/2] add non_init_kernel_text_address Srinivasa Ds
2007-12-14 6:57 ` [RFC] [patch 2/2] Refuse kprobe insertion on __init section code Srinivasa Ds
2007-12-14 7:09 ` [RFC] [patch 1/2] add non_init_kernel_text_address Andrew Morton
2007-12-14 7:51 ` Ananth N Mavinakayanahalli
2007-12-18 4:57 ` Rusty Russell
2007-12-18 6:46 ` Srinivasa Ds
2007-12-18 7:23 ` Rusty Russell
2007-12-19 5:11 ` Rusty Russell
2008-01-01 6:34 ` Srinivasa Ds [this message]
2007-12-14 9:30 ` Srinivasa Ds
2007-12-14 10:17 ` Srinivasa Ds
2007-12-14 12:46 ` Johannes Weiner
2007-12-17 10:15 ` Srinivasa Ds
2007-12-17 10:20 ` [RFC] [patch 2/2] Refuse kprobe insertion on __init section code Srinivasa Ds
2007-12-14 9:34 ` Srinivasa Ds
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=4779DEDA.90207@in.ibm.com \
--to=srinivasa@in.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=rusty@rustcorp.com.au \
/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