all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: 19067@debbugs.gnu.org
Subject: bug#19067: 24.4; temacs startup failure when both PT_PAX and XATTR_PAX flags are enabled in Linux
Date: Sun, 16 Nov 2014 12:39:02 +0100	[thread overview]
Message-ID: <21608.36054.486023.532920@a1i15.kph.uni-mainz.de> (raw)

Forwarding Gentoo bug reports https://bugs.gentoo.org/497498 and
https://bugs.gentoo.org/526948 :

On a GNU/Linux system with grsecurity/PaX enabled Linux kernel,
temacs startup will fail when both CONFIG_PAX_PT_PAX_FLAGS and
CONFIG_PAX_XATTR_PAX_FLAGS are enabled:

   if test "no" = "yes"; then \
     rm -f bootstrap-emacs; \
     ln temacs bootstrap-emacs; \
   else \
     ./temacs --batch --load loadup bootstrap || exit 1; \
     test "X/sbin/paxctl" = X || /sbin/paxctl -zex emacs; \
     mv -f emacs bootstrap-emacs; \
   fi
   /bin/sh: line 7:  1591 Killed                  ./temacs --batch --load
   loadup bootstrap
   Makefile:815: recipe for target 'bootstrap-emacs' failed
   make[1]: *** [bootstrap-emacs] Error 1
   make[1]: Leaving directory
   '/var/tmp/portage/app-editors/emacs-24.4/work/emacs-24.4/src'
   Makefile:382: recipe for target 'src' failed
   make: *** [src] Error 2

The problem is that paxctl(1) sets the "e" flag ("do not emulate
trampolines") by default for ELF binaries, but setfattr(1) doesn't.
While in principle both settings of the flag would be OK for our case,
Linux (the kernel) refuses to run the binary if the PT_PAX and
XATTR_PAX flags are inconsistent with one another.

Adding the "e" flag also to setfattr fixes this. Patch will follow.





             reply	other threads:[~2014-11-16 11:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-16 11:39 Ulrich Mueller [this message]
     [not found] ` <handler.19067.B.141613797221804.ack@debbugs.gnu.org>
2014-11-16 11:49   ` bug#19067: [PATCH] Use consistent paxctl and setfattr flags for temacs Ulrich Müller
2014-11-23 11:46     ` Ulrich Mueller

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=21608.36054.486023.532920@a1i15.kph.uni-mainz.de \
    --to=ulm@gentoo.org \
    --cc=19067@debbugs.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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.