[15937] in Kerberos_V5_Development
Re: design choices for a loadable module interface
daemon@ATHENA.MIT.EDU (Nicolas Williams)
Tue Jun 29 18:28:20 2010
Date: Tue, 29 Jun 2010 17:29:23 -0500
From: Nicolas Williams <Nicolas.Williams@oracle.com>
To: Russ Allbery <rra@stanford.edu>
Message-ID: <20100629222923.GB13124@oracle.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <20100629221226.GB11785@oracle.com>
Cc: krbdev@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On Tue, Jun 29, 2010 at 05:12:26PM -0500, Nicolas Williams wrote:
> On Tue, Jun 29, 2010 at 02:55:08PM -0700, Russ Allbery wrote:
> > > Data symbols tend to have more issues than function symbols. [...]
> >
> > Given that both MIT and Heimdal are already successfully using exported
> > data symbols as part of their ABIs, I'd like to hear more concrete details
> > of what problems this is currently causing in practice before ruling this
> > out. I assume that you're proposing moving away from this to solve some
> > set of problems that are currently affecting both major Kerberos
> > implementations?
>
> I distinctly remember issues on Windows; I just don't remember the
> details.
I've asked one of the Solaris linker aliens, and the answer was: copy
relocations. These are a problem when dlopen/dlsym are not involved and
the caller is not built as PIC code. In the case we're talking about
data symbols are not a problem.
Nico
--
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
