From: Will Deacon <will.deacon@arm.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: "linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
Mark Brown <broonie@linaro.org>,
Richard Guy Briggs <rgb@redhat.com>,
Mark Brown <broonie@kernel.org>, Eric Paris <eparis@redhat.com>,
"linux-audit@redhat.com" <linux-audit@redhat.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: audit: Fix build for audit changes
Date: Mon, 11 Aug 2014 16:47:55 +0100 [thread overview]
Message-ID: <20140811154755.GI15853@arm.com> (raw)
In-Reply-To: <20140811151502.GS24268@arm.com>
On Mon, Aug 11, 2014 at 04:15:02PM +0100, Catalin Marinas wrote:
> On Mon, Aug 11, 2014 at 02:33:38PM +0100, Will Deacon wrote:
> > On Mon, Aug 11, 2014 at 02:22:24PM +0100, Eric Paris wrote:
> > > On Mon, 2014-08-11 at 10:09 +0100, Will Deacon wrote:
> > > > On Thu, Jul 17, 2014 at 12:26:42PM +0100, Mark Brown wrote:
> > > > > From: Mark Brown <broonie@linaro.org>
> > > > >
> > > > > Commit 3efe33f5d2 (audit: x86: drop arch from __audit_syscall_entry()
> > > > > interface) removed the arch parameter from __audit_syscall_entry() and
> > > > > updated the only current user in mainline but this breaks the ARMv8 audit
> > > > > code that has been added in -next. Fix this by making the equivalent
> > > > > update to ARMv8.
> > > > >
> > > > > Signed-off-by: Mark Brown <broonie@linaro.org>
> > > > > ---
> > > > > arch/arm64/kernel/ptrace.c | 4 ++--
> > > > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > > > >
> > > > > diff --git a/arch/arm64/kernel/ptrace.c b/arch/arm64/kernel/ptrace.c
> > > > > index 70526cfda056..310842e3d477 100644
> > > > > --- a/arch/arm64/kernel/ptrace.c
> > > > > +++ b/arch/arm64/kernel/ptrace.c
> > > > > @@ -1115,8 +1115,8 @@ asmlinkage int syscall_trace_enter(struct pt_regs *regs)
> > > > > if (test_thread_flag(TIF_SYSCALL_TRACEPOINT))
> > > > > trace_sys_enter(regs, regs->syscallno);
> > > > >
> > > > > - audit_syscall_entry(syscall_get_arch(), regs->syscallno,
> > > > > - regs->orig_x0, regs->regs[1], regs->regs[2], regs->regs[3]);
> > > > > + audit_syscall_entry(regs->syscallno, regs->orig_x0, regs->regs[1],
> > > > > + regs->regs[2], regs->regs[3]);
> > > >
> > > > Eric, Richard: when is 3efe33f5d2 ("audit: x86: drop arch from
> > > > __audit_syscall_entry() interface") going to hit mainline? I've been holding
> > > > off this fix until the offending commit is merged, but if that's not going
> > > > to happen for 3.17, then we probably need to do something else to fix -next.
> > >
> > > I think I'm being lazy this window and not oging to send a pull. So
> > > I'll pick up this fix as soon as rc1 cuts in my tree.
> >
> > Oh, alright then. If you're not going to send the code for mainline, you
> > could also just drop it from -next ;)
> >
> > Anyway, if you do fix it, please let me know so that I can remove our #ifdef
> > CONFIG_AUDITSYSCALL guards (which only exist to stop build breakage in -next
> > with defconfig).
>
> Actually, Eric could carry the arm64 change from Mark into -next as well
> and we can drop the arm64 #ifdef before the API change hits mainline.
Indeed -- I think that's what we'd agreed, right?
Will
WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: audit: Fix build for audit changes
Date: Mon, 11 Aug 2014 16:47:55 +0100 [thread overview]
Message-ID: <20140811154755.GI15853@arm.com> (raw)
In-Reply-To: <20140811151502.GS24268@arm.com>
On Mon, Aug 11, 2014 at 04:15:02PM +0100, Catalin Marinas wrote:
> On Mon, Aug 11, 2014 at 02:33:38PM +0100, Will Deacon wrote:
> > On Mon, Aug 11, 2014 at 02:22:24PM +0100, Eric Paris wrote:
> > > On Mon, 2014-08-11 at 10:09 +0100, Will Deacon wrote:
> > > > On Thu, Jul 17, 2014 at 12:26:42PM +0100, Mark Brown wrote:
> > > > > From: Mark Brown <broonie@linaro.org>
> > > > >
> > > > > Commit 3efe33f5d2 (audit: x86: drop arch from __audit_syscall_entry()
> > > > > interface) removed the arch parameter from __audit_syscall_entry() and
> > > > > updated the only current user in mainline but this breaks the ARMv8 audit
> > > > > code that has been added in -next. Fix this by making the equivalent
> > > > > update to ARMv8.
> > > > >
> > > > > Signed-off-by: Mark Brown <broonie@linaro.org>
> > > > > ---
> > > > > arch/arm64/kernel/ptrace.c | 4 ++--
> > > > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > > > >
> > > > > diff --git a/arch/arm64/kernel/ptrace.c b/arch/arm64/kernel/ptrace.c
> > > > > index 70526cfda056..310842e3d477 100644
> > > > > --- a/arch/arm64/kernel/ptrace.c
> > > > > +++ b/arch/arm64/kernel/ptrace.c
> > > > > @@ -1115,8 +1115,8 @@ asmlinkage int syscall_trace_enter(struct pt_regs *regs)
> > > > > if (test_thread_flag(TIF_SYSCALL_TRACEPOINT))
> > > > > trace_sys_enter(regs, regs->syscallno);
> > > > >
> > > > > - audit_syscall_entry(syscall_get_arch(), regs->syscallno,
> > > > > - regs->orig_x0, regs->regs[1], regs->regs[2], regs->regs[3]);
> > > > > + audit_syscall_entry(regs->syscallno, regs->orig_x0, regs->regs[1],
> > > > > + regs->regs[2], regs->regs[3]);
> > > >
> > > > Eric, Richard: when is 3efe33f5d2 ("audit: x86: drop arch from
> > > > __audit_syscall_entry() interface") going to hit mainline? I've been holding
> > > > off this fix until the offending commit is merged, but if that's not going
> > > > to happen for 3.17, then we probably need to do something else to fix -next.
> > >
> > > I think I'm being lazy this window and not oging to send a pull. So
> > > I'll pick up this fix as soon as rc1 cuts in my tree.
> >
> > Oh, alright then. If you're not going to send the code for mainline, you
> > could also just drop it from -next ;)
> >
> > Anyway, if you do fix it, please let me know so that I can remove our #ifdef
> > CONFIG_AUDITSYSCALL guards (which only exist to stop build breakage in -next
> > with defconfig).
>
> Actually, Eric could carry the arm64 change from Mark into -next as well
> and we can drop the arm64 #ifdef before the API change hits mainline.
Indeed -- I think that's what we'd agreed, right?
Will
next prev parent reply other threads:[~2014-08-11 15:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 11:26 [PATCH] arm64: audit: Fix build for audit changes Mark Brown
2014-07-17 11:26 ` Mark Brown
2014-07-17 11:59 ` Catalin Marinas
2014-07-17 11:59 ` Catalin Marinas
2014-07-17 14:50 ` Mark Brown
2014-07-17 14:50 ` Mark Brown
2014-07-17 14:58 ` Catalin Marinas
2014-07-17 14:58 ` Catalin Marinas
2014-07-17 15:01 ` Mark Brown
2014-07-17 15:01 ` Mark Brown
2014-07-17 16:26 ` Richard Guy Briggs
2014-07-17 16:26 ` Richard Guy Briggs
2014-07-24 19:12 ` Mark Brown
2014-07-24 19:12 ` Mark Brown
2014-07-25 9:21 ` Catalin Marinas
2014-07-25 9:21 ` Catalin Marinas
2014-07-25 11:04 ` Mark Brown
2014-07-25 11:04 ` Mark Brown
2014-08-11 9:09 ` Will Deacon
2014-08-11 9:09 ` Will Deacon
2014-08-11 13:22 ` Eric Paris
2014-08-11 13:22 ` Eric Paris
2014-08-11 13:33 ` Will Deacon
2014-08-11 13:33 ` Will Deacon
2014-08-11 15:15 ` Catalin Marinas
2014-08-11 15:15 ` Catalin Marinas
2014-08-11 15:47 ` Will Deacon [this message]
2014-08-11 15:47 ` Will Deacon
-- strict thread matches above, loose matches on Subject: below --
2014-08-17 14:26 Mark Brown
2014-08-17 14:26 ` Mark Brown
2014-08-18 16:40 ` Catalin Marinas
2014-08-18 16:40 ` Catalin Marinas
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=20140811154755.GI15853@arm.com \
--to=will.deacon@arm.com \
--cc=broonie@kernel.org \
--cc=broonie@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=eparis@redhat.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.