From: Magnus Granberg <zorry@gentoo.org>
To: libffi-discuss@sourceware.org
Subject: Re: [Patch] Updated version of emutramp_enabled_check() for PaX kernels
Date: Thu, 27 Mar 2014 18:15:00 -0000 [thread overview]
Message-ID: <2285283.rsLvOXeDcT@laptop1.gw.ume.nu> (raw)
>Hi
>Magnus, Reading /proc/self/status is a little more heavy weight than checking
an environment variable. Do we really have to do this every time we call
dlmmap(), or can we do it once and cache the result?
>Thanks,
>AG
The selinux check read /proc/mount for selinux stuff and even check if it have
the selinux dir. I think the selinux check have the same heavy weight as the
pax check and then the selinux need to make a temp file in some dir the app
have acces to make file in. For me is fine to read /proc/... on every time.
/Magnus
next reply other threads:[~2014-03-27 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 18:15 Magnus Granberg [this message]
2014-03-28 15:43 ` Anthony Green
-- strict thread matches above, loose matches on Subject: below --
2013-04-29 21:45 Magnus Granberg
2013-05-13 17:53 ` Magnus Granberg
2013-05-22 11:50 ` Anthony Green
2013-05-22 15:16 ` Magnus Granberg
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=2285283.rsLvOXeDcT@laptop1.gw.ume.nu \
--to=zorry@gentoo.org \
--cc=libffi-discuss@sourceware.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).