All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Müller" <schnitzeltony@gmail.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Run experience with security flags enabled
Date: Wed, 26 Sep 2018 23:25:01 +0200	[thread overview]
Message-ID: <CALbNGRSPiWuTyLqaWbiH3UDF-maBQusnrbPCH_eWCxzm7n5rPA@mail.gmail.com> (raw)

Hi,

from oe-core perspective my images are build on sumo (glibc 2.27). To
see what to expect, I enabled security flags (and yes some recipes in
my layers needed rework).

Now that I have an image, I thought: let's give it a run. Apart of
other issues (maybe later) I get on every startup an error message for
ldconfig.
systemctl ldconfig says:

● ldconfig.service - Rebuild Dynamic Linker Cache
   Loaded: loaded (/lib/systemd/system/ldconfig.service; static;
vendor preset: enabled)
   Active: failed (Result: core-dump) since Mon 2018-09-24 19:05:04
UTC; 2 days ago
     Docs: man:ldconfig(8)
  Process: 136 ExecStart=/sbin/ldconfig -X (code=dumped, signal=SEGV)
 Main PID: 136 (code=dumped, signal=SEGV)

Sep 24 19:05:04 raspberrypi3 systemd[1]: Starting Rebuild Dynamic
Linker Cache...
Sep 24 19:05:04 raspberrypi3 systemd[1]: ldconfig.service: Main
process exited, code=dumped, status=11/SEGV
Sep 24 19:05:04 raspberrypi3 systemd[1]: ldconfig.service: Failed with
result 'core-dump'.
Sep 24 19:05:04 raspberrypi3 systemd[1]: Failed to start Rebuild
Dynamic Linker Cache.

Again somebody else seeing similar / remembers a fix?

Help appreciated

Andreas


             reply	other threads:[~2018-09-26 21:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-26 21:25 Andreas Müller [this message]
2018-09-26 21:46 ` Run experience with security flags enabled Khem Raj
2018-09-27 12:57   ` Dan McGregor
2018-09-27 18:42     ` Andreas Müller
2018-09-27 18:49       ` Khem Raj
2018-09-27 18:52         ` Andreas Müller

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=CALbNGRSPiWuTyLqaWbiH3UDF-maBQusnrbPCH_eWCxzm7n5rPA@mail.gmail.com \
    --to=schnitzeltony@gmail.com \
    --cc=openembedded-core@lists.openembedded.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.