linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Paris <eparis@redhat.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Will Deacon <will.deacon@arm.com>,
	Peter Ujfalusi <peter.ujfalusi@ti.com>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-audit@redhat.com" <linux-audit@redhat.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH - linux-next] ARM: ptrace: Fix audit caused compile error
Date: Tue, 21 Feb 2012 08:49:22 -0500	[thread overview]
Message-ID: <1329832162.2337.44.camel@localhost> (raw)
In-Reply-To: <1329831350.2337.43.camel@localhost>

On Tue, 2012-02-21 at 08:35 -0500, Eric Paris wrote:
> On Tue, 2012-02-21 at 13:30 +0000, Russell King - ARM Linux wrote:
> > On Tue, Feb 21, 2012 at 01:16:17PM +0000, Will Deacon wrote:
> > > On Tue, Feb 21, 2012 at 12:04:15PM +0000, Peter Ujfalusi wrote:
> > > > While trying to compile the kernel for ARM (omap2plus_defconfig) the kernel
> > > > build fails with:
> > > > 
> > > > arch/arm/kernel/ptrace.c: In function ‘syscall_trace’:
> > > > arch/arm/kernel/ptrace.c:920:3: error: implicit declaration of function ‘audit_syscall_exit’
> > > > arch/arm/kernel/ptrace.c:922:3: error: implicit declaration of function ‘audit_syscall_entry’
> > > > arch/arm/kernel/ptrace.c:922:23: error: ‘AUDIT_ARCH_ARMEB’ undeclared (first use in this function)
> > > > arch/arm/kernel/ptrace.c:922:23: note: each undeclared identifier is reported only once for each function it appears in
> > > > make[1]: *** [arch/arm/kernel/ptrace.o] Error 1
> > > > 
> > > > The issue created by commit:
> > > > 29ef73b7 Kernel: Audit Support For The ARM Platform
> > > > 
> > > > We need to include the linux/audit.h header to the arch/arm/kernel/ptrace.c
> > > > file to be able to compile the kernel.
> > > 
> > > This was already reported and I think Russell was going to revert the
> > > offending commit, since it needed some rework to handle little-endian
> > > configurations.
> > > 
> > > I can't see the revert in any of the trees I'm tracking though...
> > 
> > I never pushed that out because I thought someone was going to fix it.
> > Were any patches produced to fix it?  I can't see anything in the patch
> > system and I couldn't see anything on the list.
> > 
> > It seems the previous thread about it just died.  Oh well, I guess a
> > revert is what's required after all.
> 
> http://marc.info/?l=linux-arm-kernel&m=132928424120369&w=2
> 
> ???

You probably meant the arch endian bug.  I wrote a patch for it, but
guess i never sent it.  It was just sitting on my audit arm branch.  So
I just sent that one as well.

Thanks Russell!
-Eric

      reply	other threads:[~2012-02-21 13:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-21 12:04 [PATCH - linux-next] ARM: ptrace: Fix audit caused compile error Peter Ujfalusi
2012-02-21 13:16 ` Will Deacon
2012-02-21 13:30   ` Russell King - ARM Linux
2012-02-21 13:35     ` Eric Paris
2012-02-21 13:49       ` Eric Paris [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=1329832162.2337.44.camel@localhost \
    --to=eparis@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-audit@redhat.com \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=peter.ujfalusi@ti.com \
    --cc=sfr@canb.auug.org.au \
    --cc=will.deacon@arm.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).