From: "Rick \"Zero_Chaos\" Farina" <zerochaos@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: [gentoo-catalyst] Re: sem_open bug building python
Date: Wed, 01 Jan 2014 15:51:11 -0500 [thread overview]
Message-ID: <52C47FBF.2090105@gentoo.org> (raw)
In-Reply-To: <52C47F17.3060202@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Resending to gentoo-catalyst because I'm stupid.
- -Zero
On 01/01/2014 03:48 PM, Rick "Zero_Chaos" Farina wrote:
> Team,
>
> My builds just started failing with a known issue while building
> python. A patch was written by blueness (and backported by
> dol-sen), however, I'd like to discuss the implementation and get
> this fixed before we cut the 2.0.16 release. Here is the patch as
> it stands:
>
> X-Git-Url:
> http://git.overlays.gentoo.org/gitweb/?p=proj%2Fcatalyst.git;a=blobdiff_plain;f=modules%2Fgeneric_stage_target.py;h=9edafe99f83a8a6f4f1ef8e60f2b54e59dc95963;hp=848aca2f8616574ce1a8cdc0d1c4cf33c6620bb8;hb=648c9cc9bfdf88e3612399f2cc9bed9a3bae17f5;hpb=5fb71eb045f0b1b8252b85ce9e8042c87a9bdb1a
>
> diff --git a/modules/generic_stage_target.py
> b/modules/generic_stage_target.py index 848aca2..9edafe9 100644 ---
> a/modules/generic_stage_target.py +++
> b/modules/generic_stage_target.py @@ -174,16 +174,21 @@ class
> generic_stage_target(generic_target):
>
> """ Setup our mount points """ if "SNAPCACHE" in self.settings: -
>
> self.mounts=["/proc","/dev","/usr/portage","/usr/portage/distfiles","/var/tmp/portage"]
>
>
+ self.mounts=["/proc", "/dev", "/usr/portage",
> + "/usr/portage/distfiles", "/var/tmp/portage"]
> self.mountmap={"/proc":"/proc","/dev":"/dev","/dev/pts":"/dev/pts",\
>
>
"/usr/portage":self.settings["snapshot_cache_path"]+"/portage",\
> -
> "/usr/portage/distfiles":self.settings["distdir"],"/var/tmp/portage":"tmpfs"}
>
>
+
> "/usr/portage/distfiles":self.settings["distdir"],"/var/tmp/portage":"tmpfs",
>
>
+ "/dev/shm": "/dev/shm"}
> else: -
> self.mounts=["/proc","/dev","/usr/portage/distfiles","/var/tmp/portage"]
>
>
+ self.mounts=["/proc", "/dev", "/usr/portage/distfiles",
> + "/var/tmp/portage"]
> self.mountmap={"/proc":"/proc","/dev":"/dev","/dev/pts":"/dev/pts",\
>
>
- -
> "/usr/portage/distfiles":self.settings["distdir"],"/var/tmp/portage":"tmpfs"}
>
>
+
> "/usr/portage/distfiles":self.settings["distdir"],"/var/tmp/portage":"tmpfs",
>
>
+ "/dev/shm": "/dev/shm"}
> if os.uname()[0] == "Linux": self.mounts.append("/dev/pts") +
> self.mounts.append("/dev/shm")
>
> self.set_mounts()
>
>
> I'm not a fan of this because /dev/shm is writable, and we are
> sharing /dev/shm with not only the host, but all the other catalyst
> runs (in my case that is up to 3) which means it is entirely
> possible for writes to collide, or worse, cleanup to collide.
>
> Simply chaning the second "/dev/shm" to "tmpfs" is also not right
> because it ends up with the wrong permissions:
>
> shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime) tmpfs
> on /catalyst/tmp/hardened/stage1-amd64-2013.0/dev/shm type tmpfs
> (rw,relatime,size=20971520k)
>
>
> I'd like to have the patch rewritten to mount this properly as it's
> own tmpfs with the proper mount options.
>
> Does anyone have issues with this? It is a rather trivial thing to
> copy from my work making /var/tmp/portage a tmpfs, anyone can do
> the work. I can do it, or whomever.
>
> Please discuss quickly, I fear this bug will stop all forward
> progress and we really can't afford for the builds to stop, again.
> I know I can't.
>
> Thanks, Zero
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJSxH+/AAoJEKXdFCfdEflKk/EP/RiGZwZV+vg+VB3E0pFPJww9
RdIy7zPDTxjQ4GVczUqUF9DEOBJ0zXRoNKiwpKWhyxK6I2wIYFBrggnQY8duLmX3
GUBLlprwtFfOYGOLJIFibsIamKHEIHXRgs8PGwEPyG0qiqA2N+uFVbgi8m/Vsp0/
MRhm1Rd8gclWzAyJ/RJaTm6OIWOKcUklgYEmwADoXzFOpROdR3N7GqHyz6XzUPlZ
kx+DuVCMaVFXMIHFJHSMTKC2RlQP7ZAhB0MGV/0rppFOM0EIV4DizVHKlkNXB9jE
MBgXC1grg2cCX7FrKx7NXX37aN6LtgFYdCjPOesnteCe8kCn03MFqAF9/b3grqIG
/d0LcTdAUjXFZoh37EjhvhWPvJu3qkm+9JDmtaqRYC3Ygn5iuXxCc8e9GbWA5rhi
eSZofGls2kzoEQsDYngpdIRmVxru+qtXBDwb7InmRzpDW6UcVBBPc4vEq+3i09br
qPLmSEJDo8eVTkQr9A5GFpzPIese6drSPlA8+4GiLIgbgMpL8p3+nHUey3Akg9RS
aEWd6KmhxE8bZvTHo2RgVhQotkUz3mf4YI/JP7JCzWh/WIj1E4tMzxfhT7zS2nxY
eAo+NHSmWcI393ysghX6mACg43mLZSQ9d51KrnlcqAsHt60VarDQ/7+6paIF5puY
TaBl9SDTfSkFbJ6CsM85
=9Tj7
-----END PGP SIGNATURE-----
parent reply other threads:[~2014-01-01 20:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <52C47F17.3060202@gentoo.org>]
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=52C47FBF.2090105@gentoo.org \
--to=zerochaos@gentoo.org \
--cc=gentoo-catalyst@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox