From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: vagabon.xyz@gmail.com, ralf@linux-mips.org, linux-mips@linux-mips.org
Subject: Re: [PATCH] Remove mfinfo[64] used by get_wchan()
Date: Fri, 18 Aug 2006 10:50:01 +0200 [thread overview]
Message-ID: <44E57F39.2020009@innova-card.com> (raw)
In-Reply-To: <20060818.171558.89065994.nemoto@toshiba-tops.co.jp>
Atsushi Nemoto wrote:
> On Fri, 18 Aug 2006 09:50:57 +0200, Franck Bui-Huu <vagabon.xyz@gmail.com> wrote:
>>>> + unsigned long size = 0;
>>> You must pass some non-zero size even if CONFIG_KALLSYMS was not set.
>>> Otherwise schedule_mfi will not be initialized as expected. Actually,
>>> this is not a problem of this patch, but we missed this point on
>>> previous cleanups for the get_frame_info()...
>> or maybe we can just fix get_frame_info() and make it more robust ?
>
> Maybe. But info->func_size == 0 is valid input when it was called via
> show_backtrace. If an exception occured on a first instruction of a
> function, get_frame_info() should return 1. So it would be easy to
> give some appropriate (128?) size here.
>
Does something like this seem correct ? If an exception occured on a first
instruction of a function, show_backtrace() will call get_frame_info()
with info->func_size != 0 but very small. In this case it returns 1.
If the caller of get_frame_info() set info->func_size = 0, then it doesn't
know the size of the function, and we assume it to 128 instructions.
Franck
-- >8 --
diff --git a/arch/mips/kernel/process.c b/arch/mips/kernel/process.c
index 951bf9c..5b18806 100644
--- a/arch/mips/kernel/process.c
+++ b/arch/mips/kernel/process.c
@@ -311,12 +311,19 @@ static inline int is_sp_move_ins(union m
static int get_frame_info(struct mips_frame_info *info)
{
union mips_instruction *ip = info->func;
- int i, max_insns =
- min(128UL, info->func_size / sizeof(union mips_instruction));
+ unsigned max_insns = info->func_size / sizeof(union mips_instruction);
+ unsigned i;
info->pc_offset = -1;
info->frame_size = 0;
+ if (!ip)
+ goto err;
+
+ if (max_insns == 0)
+ max_insns = 128U;
+ max_insns = min(128U, max_insns);
+
for (i = 0; i < max_insns; i++, ip++) {
if (is_jal_jalr_jr_ins(ip))
@@ -337,6 +344,7 @@ static int get_frame_info(struct mips_fr
if (info->pc_offset < 0) /* leaf */
return 1;
/* prologue seems boggus... */
+err:
return -1;
}
next prev parent reply other threads:[~2006-08-18 8:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-17 13:57 [PATCH] Remove mfinfo[64] used by get_wchan() Franck Bui-Huu
2006-08-18 2:52 ` Atsushi Nemoto
2006-08-18 7:50 ` Franck Bui-Huu
2006-08-18 8:15 ` Atsushi Nemoto
2006-08-18 8:50 ` Franck Bui-Huu [this message]
2006-08-18 9:11 ` Atsushi Nemoto
2006-08-18 12:17 ` Franck Bui-Huu
2006-08-18 14:04 ` Atsushi Nemoto
2006-08-18 14:13 ` Franck Bui-Huu
2006-08-18 14:41 ` Atsushi Nemoto
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=44E57F39.2020009@innova-card.com \
--to=vagabon.xyz@gmail.com \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.