public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Samuli Suominen <ssuominen@gentoo.org>
To: libffi-discuss@sourceware.org, hardened@gentoo.org, zorry@gentoo.org
Subject: Re: libffi 3.1-rc1 needs testing!
Date: Thu, 27 Mar 2014 12:40:00 -0000	[thread overview]
Message-ID: <53341B11.6080805@gentoo.org> (raw)
In-Reply-To: <87a9ce3ry7.fsf@moxielogic.com>

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


On 25/03/14 23:10, Anthony Green wrote:
> It's here: ftp://sourceware.org/pub/libffi/libffi-3.1-rc1.tar.gz
>
>

This patch is missing from the 3.1-rc1 release:

https://sourceware.org/ml/libffi-discuss/2013/msg00130.html

I'll attach it here too.

[-- Attachment #2: libffi-3.0.13-emutramp_pax_proc.patch --]
[-- Type: text/x-patch, Size: 911 bytes --]

2013-05-22  Magnus Granberg  <zorry@gentoo.org>

	#457194
	* src/closuer.c (emutramp_enabled_check): Check with /proc.

--- a/src/closures.c	2013-03-17 23:27:11.000000000 +0100
+++ b/src/closures.c	2013-04-29 23:26:02.279022022 +0200
@@ -181,10 +181,26 @@ static int emutramp_enabled = -1;
 static int
 emutramp_enabled_check (void)
 {
-  if (getenv ("FFI_DISABLE_EMUTRAMP") == NULL)
-    return 1;
-  else
+  char *buf = NULL;
+  size_t len = 0;
+  FILE *f;
+  int ret;
+  f = fopen ("/proc/self/status", "r");
+  if (f == NULL)
     return 0;
+  ret = 0;
+
+  while (getline (&buf, &len, f) != -1)
+    if (!strncmp (buf, "PaX:", 4))
+      {
+        char emutramp;
+        if (sscanf (buf, "%*s %*c%c", &emutramp) == 1)
+          ret = (emutramp == 'E');
+        break;
+      }
+  free (buf);
+  fclose (f);
+  return ret;
 }
 
 #define is_emutramp_enabled() (emutramp_enabled >= 0 ? emutramp_enabled \

  parent reply	other threads:[~2014-03-27 12:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-01 23:49 libffi 3.0.14-rc0 " Anthony Green
2014-03-01 23:56 ` Anthony Green
2014-03-03 12:44 ` Dominik Vogt
2014-03-03 19:17 ` David Fang
2014-03-04  7:29 ` Will Newton
2014-03-05  0:31   ` Alan Hourihane
2014-03-04 22:14 ` Matthias Klose
2014-03-25 21:11 ` libffi 3.1-rc1 " Anthony Green
2014-03-27 12:23   ` Dominik Vogt
2014-03-27 12:25     ` Dominik Vogt
2014-03-27 12:31   ` Dominik Vogt
2014-03-27 12:40   ` Samuli Suominen [this message]
2014-03-27 12:45     ` Samuli Suominen
2014-03-27 12:55   ` Samuli Suominen
2014-03-28 15:43     ` Anthony Green
2014-03-28 15:05   ` James Greenhalgh
2014-03-28 17:33     ` Anthony Green
2014-04-24 12:47       ` Marcus Shawcroft
2014-03-28 20:37   ` Andreas Tobler
2014-03-28 20:39   ` Matthias Klose
2014-03-28 21:56     ` Anthony Green
2014-03-28 22:31       ` Anthony Green
2014-03-29 14:25     ` ABI breakage (Was: libffi 3.1-rc1 needs testing!) Anthony Green
2014-05-30 12:21       ` Matthias Klose

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=53341B11.6080805@gentoo.org \
    --to=ssuominen@gentoo.org \
    --cc=hardened@gentoo.org \
    --cc=libffi-discuss@sourceware.org \
    --cc=zorry@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).