unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Greg Troxel <gdt@lexort.com>
To: guile-devel <guile-devel@gnu.org>
Subject: JIT and pax mprotect
Date: Thu, 27 Aug 2020 15:28:39 -0400	[thread overview]
Message-ID: <rmift87sxaw.fsf@s1.lexort.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 899 bytes --]


In trying to build 3.0.2 on NetBSD 8, I get a permission denied failure
in JIT, because of PaX MPROTECT.  Disabling that (in the individual
file, or globally) allows things to work.   This is a security feature
that prevents  making writable mappings executable.

I would expect this to run into the same problem on GNU/Linux systems.
Has anyone run into that, and is there an accomodation for this?   A
quick egrep -R of the sources doesn't turn up anything.

I am guessing that basically the link line for guile should be doing:

  if OS in (NetBSD, ?):
     paxctl +m libguile/.libs/guile

pkgsrc's build recipe does this for the final binary, but guile is built
and then used during the build step.

(Also, it might be nice to have a nicer exit than a core dump in the
presence of mprotect, but that's not that important.)

(Will update to 3.0.3, but probably that is the same).

Thanks,
Greg


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]

                 reply	other threads:[~2020-08-27 19:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=rmift87sxaw.fsf@s1.lexort.com \
    --to=gdt@lexort.com \
    --cc=guile-devel@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).