From: Anthony Green <green@moxielogic.com>
To: Gaash Hazan <gaash@qwilt.com>
Cc: Andrew Haley <aph@redhat.com>, libffi-discuss@sourceware.org
Subject: Re: libffi & fork
Date: Sun, 29 Apr 2012 17:58:00 -0000 [thread overview]
Message-ID: <CACxje5_GtnvUe_BeqYPKPdz6s9RTZC0QD43GJSv1fJZ-=JTHdQ@mail.gmail.com> (raw)
In-Reply-To: <CAP+vr+MhMzK=-gQ-Nz-avPcCfEgVPwQ7KyaOjFK4TKspyKBHdg@mail.gmail.com>
On Sun, Apr 29, 2012 at 11:34 AM, Gaash Hazan <gaash@qwilt.com> wrote:
> The selinux detected problem was fixed in
> https://github.com/atgreen/libffi/commit/eaf444eabc4c78703c0f98ac0197b1619c1b1bef#src/closures.c
> (closures.c line 149)
>
> Unfortunately Redhat 6.2 and 6.3-bets uses libffi 3.0.5 that has this problem.
Thanks Gaash.
Andrew - it would be nice if we could upgrade RHEL's libffi to a
non-ABI breaking 3.0.10. If, however, it makes more sense to
cherry-pick patches since 3.0.5, I can see some nice ones from mjw and
jakub back in 2010, and there are likely more. If you think we should
open an RFE I can propose some specific patches for consideration.
There may only be 4 or 5 and they are all pretty obvious.
AG
next prev parent reply other threads:[~2012-04-29 17:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP+vr+PX9gw7Ot6Zc7AN8Gks9P+WHVQg8bX5S7YRnTRyRBHp7A@mail.gmail.com>
2012-04-24 19:41 ` Gaash Hazan
2012-04-25 9:11 ` Andrew Haley
2012-04-25 17:33 ` Gaash Hazan
2012-04-26 10:00 ` Andrew Haley
2012-04-29 15:34 ` Gaash Hazan
2012-04-29 17:58 ` Anthony Green [this message]
2012-04-30 8:32 ` Andrew Haley
2012-04-30 19:16 ` Anthony Green
2012-05-01 7:56 ` Andrew Haley
2012-05-02 20:23 ` Anthony Green
2012-05-04 9:00 ` Andrew Haley
2012-05-05 13:19 ` Anthony Green
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='CACxje5_GtnvUe_BeqYPKPdz6s9RTZC0QD43GJSv1fJZ-=JTHdQ@mail.gmail.com' \
--to=green@moxielogic.com \
--cc=aph@redhat.com \
--cc=gaash@qwilt.com \
--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).