All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: rscholz@hrzpub.tu-darmstadt.de (Ruediger Scholz)
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] 2.6.0-test1-pa1 crashes on 715/100
Date: Sat, 19 Jul 2003 16:43:16 -0400 (EDT)	[thread overview]
Message-ID: <200307192043.h6JKhHvH002128@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <3F19A776.2040001@hrzpub.tu-darmstadt.de> from "Ruediger Scholz" at Jul 19, 2003 10:17:58 pm

> >Check the list for a kernel patch to avoid this.  The 3.2 branch has
> >canonicalize_funcptr_for_compare.  Debian 3.0.4 doesn't.
> >
> But it was accidently compiled with gcc-3.3.1. Is this kernelpatch also 
> for gcc-3.3?

All hppa-linux versions from 3.2 on have canonicalize_funcptr_for_compare.
This fixes the comparison of function pointers in user space.  However,
the version of canonicalize_funcptr_for_compare in libgcc.a isn't suitable
for the kernel.

This arises because function pointers are implemented using pointers
to non-unique function descriptors.  -1 to 4095 are also special.
This is allowed in the C standard but the current kernel code doesn't
take this into account when comparing function pointers.  The only
other linux port to use function descriptors is ia64 and I believe
that its function pointers are unique, so no special code is needed
to resolve the pointers.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

      reply	other threads:[~2003-07-19 20:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-19 19:23 [parisc-linux] 2.6.0-test1-pa1 crashes on 715/100 Ruediger Scholz
2003-07-19 20:12 ` John David Anglin
2003-07-19 20:17   ` Ruediger Scholz
2003-07-19 20:43     ` John David Anglin [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=200307192043.h6JKhHvH002128@hiauly1.hia.nrc.ca \
    --to=dave@hiauly1.hia.nrc.ca \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=rscholz@hrzpub.tu-darmstadt.de \
    /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.