From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2019-02-14
Date: Wed, 20 Feb 2019 09:08:29 +0100 [thread overview]
Message-ID: <20190220090829.6cb610b0@windsurf> (raw)
In-Reply-To: <a1b02faf-5b05-b7fd-a311-4dc0a5bc8fd4@mind.be>
Arnout,
On Tue, 19 Feb 2019 23:14:33 +0100
Arnout Vandecappelle <arnout@mind.be> wrote:
> > Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> >> arm | runc-v1.0.0-rc6 | http://autobuild.buildroot.net/results/63e9d88ae5177541be463f1e2aafec59aa410479
> >> i686 | runc-v1.0.0-rc6 | http://autobuild.buildroot.net/results/f71ddcd17f4991a3caeaac42c81ed97bdf847718
> >> arm | runc-v1.0.0-rc6 | http://autobuild.buildroot.net/results/64ecdb1e007106fdb05979b10b42b90591255504
> >> arm | runc-v1.0.0-rc6 | http://autobuild.buildroot.net/results/c359954d671e338997615d3a2f3aca168a53cb91
> >>
> >
> > This is relating to O_TMPFILE not being available with this configuration:
> >
> > libcontainer/nsenter/cloned_binary.c:206
> > #ifdef HAVE_MEMFD_CREATE
> > memfd = memfd_create(RUNC_MEMFD_COMMENT, MFD_CLOEXEC | MFD_ALLOW_SEALING);
> > #else
> > memfd = open("/tmp", O_TMPFILE | O_EXCL | O_RDWR | O_CLOEXEC, 0711);
> > #endif
> >
> > I'm not aware of what the best alternative to O_TMPFILE in this system
> > setup would be. Do you (or anyone else) know a good solution to patch in
> > here for compatibility?
>
> O_TMPFILE was added in Linux 3.11, memfd some time later IIRC. So depending on
> BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_11 seems the correct approach.
Those failures are happening with a toolchain that uses 3.12 kernel
headers.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-02-20 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5c666398.1c69fb81.1f9f6.2db0SMTPIN_ADDED_MISSING@mx.google.com>
2019-02-19 0:01 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2019-02-14 Christian Stewart
2019-02-19 22:14 ` Arnout Vandecappelle
2019-02-20 8:08 ` Thomas Petazzoni [this message]
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=20190220090829.6cb610b0@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.