All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: pthreads should rdepend on libgcc
Date: Thu, 14 Nov 2019 13:22:17 +0200	[thread overview]
Message-ID: <20191114112217.GA13971@localhost> (raw)
In-Reply-To: <CAMKF1srtAu02xK-7QWcnrPsgJ8qCWRLnGc2FKnDZCXAYtui9Ww@mail.gmail.com>

On Wed, Nov 13, 2019 at 02:36:56PM -0800, Khem Raj wrote:
>...
> however, there could be another problem, where libgcc_s is lazily
> loaded during pthread_exit and
> application is not using root user which many daemons do where they
> use less privileged user to run
> and it would fail in the exact same manner. I also see few other uses
> of libgcc_s.so being dlopened in
> nptl unwind code and libbacktrace in glibc.
>...

Why would this be a problem?

dlopen() does not require root privileges.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



  parent reply	other threads:[~2019-11-14 11:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-13  8:34 pthreads should rdepend on libgcc Bartosz Golaszewski
2019-11-13 15:04 ` Mark Hatle
2019-11-13 15:50   ` Ross Burton
2019-11-13 22:36     ` Khem Raj
2019-11-14 11:01       ` Bartosz Golaszewski
2019-11-14 11:22       ` Adrian Bunk [this message]
2019-11-13 21:03   ` Bartosz Golaszewski
2019-11-13 21:58     ` Richard Purdie
2019-11-13 22:38 ` Khem Raj
2019-11-14 11:00   ` Bartosz Golaszewski

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=20191114112217.GA13971@localhost \
    --to=bunk@stusta.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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.