protected data in a DSO with copy relocation
Ondřej Bílka
neleai@seznam.cz
Thu Dec 18 19:50:00 GMT 2014
On Wed, Dec 17, 2014 at 03:22:53PM -0800, H.J. Lu wrote:
> On Wed, Dec 17, 2014 at 2:53 PM, Roland McGrath <roland@hack.frob.com> wrote:
> >> I'd like to have a decision on
> >>
> >> https://sourceware.org/bugzilla/show_bug.cgi?id=17711
> >>
> >> If we want to support protected data in a DSO with copy relocation,
> >> which will incur run-time and memory overhead, I can prepare ld.so
> >> as well as linker patches. Otherwise, I will make a linker patch
> >> to disallow protected data in a DSO with copy relocation.
> >
> > I think we certainly shouldn't do any rtld changes for this in the current
> > cycle. If we can just punt thinking about it at all until after this
>
> If we punt, we need to update the elf/vismain test which fails with
> the current ld.
>
> > release, that would be best. If we need some kind of decision sooner, then
> > my inclination is to say that STV_PROTECTED is not useful enough to spend
> > effort on supporting its corner cases. I'm not aware of uses cases for it
> > that both appear in the real world and are actually worthwhile. But if
> > there is no urgent need, then let's discuss this in detail after the release.
>
> I agree.
>
I also think it should not be supported. I see another potential problem
that it makes maintainance harder, for example uses it and forgots bump
Makefile requirements then when somebody with older system will run to
this problem.
More information about the Libc-alpha
mailing list