From: Dave Anderson <anderson@redhat.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: insmod bug causes kernel unwind failures for module text
Date: Wed, 31 Jul 2002 17:33:15 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905866@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905853@msgid-missing>
This one works just fine -- ship it!
Thanks,
Dave Anderson
Keith Owens wrote:
> On Tue, 30 Jul 2002 09:35:12 -0400,
> Dave Anderson <anderson@redhat.com> wrote:
> >Unfortunately the patch won't work, at least in the context of the current
> >kernel code, because the following range check in ia64_module_init() causes
> >the insmod to fail:
>
> Not sure why it worked for me, probably operator error. Revert
> segment_base to start of first section. Against a clean modutils
> 2.4.18.
>
> Index: 18.2/obj/obj_ia64.c
> --- 18.2/obj/obj_ia64.c Fri, 01 Mar 2002 11:39:06 +1100 kaos (modutils-2.4/c/0_obj_ia64.c 1.5 644)
> +++ 19.6(w)/obj/obj_ia64.c Wed, 31 Jul 2002 10:41:20 +1000 kaos (modutils-2.4/c/0_obj_ia64.c 1.8 644)
> @@ -911,12 +911,8 @@ arch_apply_relocation(struct obj_file *f
>
> case R_IA64_SEGREL32LSB : /* @segrel(sym + add), data4 LSB */
> case R_IA64_SEGREL64LSB : /* @segrel(sym + add), data8 LSB */
> - if (targsec->header.sh_type & SHT_NOBITS)
> - v = ifile->bss - v;
> - else if (targsec->header.sh_flags & SHF_EXECINSTR)
> - v = ifile->text - v;
> - else
> - v = ifile->data - v;
> + /* Only one segment for modules, see segment_base in arch_archdata */
> + v -= f->sections[1]->header.sh_addr;
> if (r_info = R_IA64_SEGREL32LSB)
> COPY_32LSB(loc, v);
> else
prev parent reply other threads:[~2002-07-31 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 8:28 [Linux-ia64] Re: insmod bug causes kernel unwind failures for module text Keith Owens
2002-07-30 13:35 ` Dave Anderson
2002-07-30 14:03 ` Dave Anderson
2002-07-31 1:09 ` Keith Owens
2002-07-31 17:33 ` Dave Anderson [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=marc-linux-ia64-105590701905866@msgid-missing \
--to=anderson@redhat.com \
--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