From: Masami Hiramatsu <hiramatu@sdl.hitachi.co.jp>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC][PATCH]fix search_extable() to find correct entry
Date: Fri, 16 Jun 2006 15:11:10 +0000 [thread overview]
Message-ID: <4492CA0E.7050308@sdl.hitachi.co.jp> (raw)
In-Reply-To: <44916017.5050006@sdl.hitachi.co.jp>
Hi,
Chen, Kenneth W wrote:
> Masami Hiramatsu wrote on Thursday, June 15, 2006 6:27 AM
>> I found a suspicious buggy code in the linux kernel on IA64 arch.
>> As far as I can see, search_extable() doesn't work correctly, because
>> the lookup routine expects that the address format of the
>> exception_table_entry is "IP + slot", but the compiler (gcc-3.4.5)
>> generates it as "IP + (slot << 2)". Thus the lookup routine always
>> fails to find the corresponding entry.
>> You can check it by dumping __ex_table section of vmlinux.
>
> Chen, Kenneth W wrote on Thursday, June 15, 2006 2:22 PM
>> But the tag address in the table is also bundle aligned, which I will
>> look a bit more.
>
> I've double checked (triple checked with sample test code below). It's a
> false alarm. Everyone should rest assure that exception table and compiler
> do match and generates correct code. There is no bug AFAICT.
Thank you for your comments.
I had just checked the dump of __ex_table section of vmlinux.
This time, I checked the __ex_table of running kernel.
It is true that those format is "IP + slot". So you are right.
I admit my mistake.
Please dispose the previous patch.
Thanks again.
--
Masami HIRAMATSU
2nd Research Dept.
Hitachi, Ltd., Systems Development Laboratory
E-mail: hiramatu@sdl.hitachi.co.jp
prev parent reply other threads:[~2006-06-16 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 13:26 [RFC][PATCH]fix search_extable() to find correct entry Masami Hiramatsu
2006-06-15 17:17 ` David Mosberger-Tang
2006-06-15 21:21 ` Chen, Kenneth W
2006-06-16 0:48 ` Chen, Kenneth W
2006-06-16 15:11 ` Masami Hiramatsu [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=4492CA0E.7050308@sdl.hitachi.co.jp \
--to=hiramatu@sdl.hitachi.co.jp \
--cc=linux-ia64@vger.kernel.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