From: Will Deacon <will.deacon@arm.com>
To: Eric Paris <eparis@redhat.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Axel Lin <axel.lin@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Nathaniel Husted <nhusted@gmail.com>,
Dave Martin <dave.martin@linaro.org>,
Nicolas Pitre <nicolas.pitre@linaro.org>,
Ingo Molnar <mingo@elte.hu>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: ptrace: Include linux/audit.h to fix build errors
Date: Wed, 15 Feb 2012 17:14:15 +0000 [thread overview]
Message-ID: <20120215171415.GE29319@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <1329325622.2337.13.camel@localhost>
On Wed, Feb 15, 2012 at 05:07:02PM +0000, Eric Paris wrote:
> Fixing the arch flag to be correct means we could do that translation
> properly. I haven't seen the patches to support translation of arm raw
> bits to something higher level in audit userspace, but I assume it's
> coming as soon as someone cares.
>
> So if someone tells me how the code knows it's endianness I'll gladly
> write the ifdef to switch from AUDIT_ARCH_ARMEB to AUDIT_ARCH_ARM when
> appropriate....
You should just be able to use #ifdef __ARMEB__ for the big-endian case (we
don't support a little-endian kernel with a big-endian userspace or anything
funky like that). If Russell has reverted the original patch your best bet is
probably to spin a v2 of the ARM bits and post it to LAK.
Will
next prev parent reply other threads:[~2012-02-15 17:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 5:36 Axel Lin
2012-02-15 8:36 ` Russell King - ARM Linux
2012-02-15 9:52 ` Will Deacon
2012-02-15 10:18 ` Russell King - ARM Linux
2012-02-15 15:10 ` Eric Paris
2012-02-15 16:10 ` Russell King - ARM Linux
2012-02-15 16:14 ` Nathaniel Husted
2012-02-15 17:07 ` Eric Paris
2012-02-15 17:14 ` Will Deacon [this message]
2012-02-15 17:34 ` Russell King - ARM Linux
2012-02-15 19:57 ` Eric Paris
2012-02-15 20:19 ` Nicolas Pitre
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=20120215171415.GE29319@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=axel.lin@gmail.com \
--cc=dave.martin@linaro.org \
--cc=eparis@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@elte.hu \
--cc=nhusted@gmail.com \
--cc=nicolas.pitre@linaro.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
Powered by JetHome