From: "Daniel P. Berrange" <berrange@redhat.com>
To: Colin Walters <walters@verbum.org>
Cc: SELinux List <selinux@tycho.nsa.gov>,
dwalsh@redhat.com, eparis@redhat.com
Subject: Re: libselinux's __attribute__((constructor)) versus nVidia libGL.so
Date: Wed, 28 Aug 2013 11:06:13 +0100 [thread overview]
Message-ID: <20130828100612.GI15706@redhat.com> (raw)
In-Reply-To: <1377625674.20072.5.camel@localhost>
On Tue, Aug 27, 2013 at 01:47:54PM -0400, Colin Walters wrote:
> This bug:
>
> https://bugzilla.gnome.org/show_bug.cgi?id=706836
FWIW, you can define "priority" values on the constructor attributes, to
sort out ordering between libraries, but this sucks as a general purpose
solution as it requires co-ordination of priorities between different a
projects. eg you might fix the selinux vs nvidia problem now, but it can
recur with any other library using constructors in the future. IMHO it
would be better to use pthread_once to do any one time initialization
of library code
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2013-08-28 10:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 17:40 libselinux's __attribute__((constructor)) versus nVidia libGL.so Colin Walters
2013-08-27 17:47 ` Colin Walters
2013-08-28 10:06 ` Daniel P. Berrange [this message]
2013-08-29 12:51 ` Stephen Smalley
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=20130828100612.GI15706@redhat.com \
--to=berrange@redhat.com \
--cc=dwalsh@redhat.com \
--cc=eparis@redhat.com \
--cc=selinux@tycho.nsa.gov \
--cc=walters@verbum.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 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.