From: Paul Moore <paul@paul-moore.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: [PATCH] audit: add ppc64 mach support
Date: Tue, 02 Dec 2014 18:19:07 -0500 [thread overview]
Message-ID: <7591024.l2V3V75FWS@sifl> (raw)
In-Reply-To: <20141202212724.GA12425@madcap2.tricolour.ca>
On Tuesday, December 02, 2014 04:27:24 PM Richard Guy Briggs wrote:
> On 14/12/02, Paul Moore wrote:
> > On Monday, December 01, 2014 03:58:09 PM Tony Jones wrote:
> > > Mainline kernel reports ppc64le (per
> > > a0588015deab1844261b27a67ae6f5b910fe2830) but there is no matching
> > > AUDIT_ARCH_PPC64LE. Eric just pinged me on irc about it. Fix to add
> > > it
> > > to include/uapi/linux/audit.h shoudld probably go upstream.
> >
> > Untested, uncompiled too, but beyond the patch below, is there anything
> > else we would need in the kernel to enable proper ppc64le support?
>
> Which kernel are you using? syscall_get_arch() already exists on
> powerpc. audit_syscall_entry() lost its first argument recently...
That patch was on top of the linux-audit tree, it's based on v3.16 so I
imagine there have been some changes upstream over the past few months.
> What if it is in compatibility mode?
/me shrugs ... that's why I posted it asking for feedback ;) I just wanted to
get the ball rolling on a fix.
--
paul moore
www.paul-moore.com
prev parent reply other threads:[~2014-12-02 23:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 20:16 [PATCH] audit: add ppc64 mach support Tony Jones
2014-08-29 20:24 ` Tony Jones
2014-09-02 15:20 ` Steve Grubb
2014-12-01 22:09 ` Steve Grubb
2014-12-01 23:58 ` Tony Jones
2014-12-02 20:18 ` Paul Moore
2014-12-02 20:29 ` Steve Grubb
2014-12-02 21:27 ` Tony Jones
2014-12-02 21:27 ` Richard Guy Briggs
2014-12-02 23:19 ` Paul Moore [this message]
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=7591024.l2V3V75FWS@sifl \
--to=paul@paul-moore.com \
--cc=linux-audit@redhat.com \
--cc=rgb@redhat.com \
/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 NNTP newsgroup(s).