Re: linux-next: manual merge of the tip tree with the audit tree

2014-09-27 Thread Stephen Rothwell
Hi Andy, On Fri, 26 Sep 2014 11:02:27 -0700 Andy Lutomirski wrote: > > I don't think that more cleanup is possible after all. > do_audit_syscall_entry may not need to pass the arch parameter to the > audit code, but it still needs it to choose the set of registers to > use. Yes, indeed, I did

Re: linux-next: manual merge of the tip tree with the audit tree

2014-09-27 Thread Stephen Rothwell
Hi Andy, On Fri, 26 Sep 2014 11:02:27 -0700 Andy Lutomirski l...@amacapital.net wrote: I don't think that more cleanup is possible after all. do_audit_syscall_entry may not need to pass the arch parameter to the audit code, but it still needs it to choose the set of registers to use. Yes,

Re: linux-next: manual merge of the tip tree with the audit tree

2014-09-26 Thread Andy Lutomirski
On Tue, Sep 23, 2014 at 10:47 PM, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the tip tree got a conflict in > arch/x86/kernel/ptrace.c between commit 91397401bb50 ("ARCH: AUDIT: > audit_syscall_entry() should not require the arch") from the audit tree > and commit

Re: linux-next: manual merge of the tip tree with the audit tree

2014-09-26 Thread Richard Guy Briggs
On 14/09/24, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the tip tree got a conflict in > arch/x86/kernel/entry_64.S between commit b4f0d3755c5e ("audit: x86: > drop arch from __audit_syscall_entry() interface") from the audit tree > and commit 1dcf74f6edfc ("x86_64, entry:

Re: linux-next: manual merge of the tip tree with the audit tree

2014-09-26 Thread Richard Guy Briggs
On 14/09/24, Stephen Rothwell wrote: Hi all, Today's linux-next merge of the tip tree got a conflict in arch/x86/kernel/entry_64.S between commit b4f0d3755c5e (audit: x86: drop arch from __audit_syscall_entry() interface) from the audit tree and commit 1dcf74f6edfc (x86_64, entry: Use

Re: linux-next: manual merge of the tip tree with the audit tree

2014-09-26 Thread Andy Lutomirski
On Tue, Sep 23, 2014 at 10:47 PM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, Today's linux-next merge of the tip tree got a conflict in arch/x86/kernel/ptrace.c between commit 91397401bb50 (ARCH: AUDIT: audit_syscall_entry() should not require the arch) from the audit tree and

Re: linux-next: manual merge of the tip tree with the audit tree

2014-09-24 Thread Andy Lutomirski
On Wed, Sep 24, 2014 at 11:12 AM, Andy Lutomirski wrote: > On Tue, Sep 23, 2014 at 10:47 PM, Stephen Rothwell > wrote: >> Hi all, >> >> Today's linux-next merge of the tip tree got a conflict in >> arch/x86/kernel/ptrace.c between commit 91397401bb50 ("ARCH: AUDIT: >> audit_syscall_entry()

Re: linux-next: manual merge of the tip tree with the audit tree

2014-09-24 Thread Andy Lutomirski
On Tue, Sep 23, 2014 at 10:47 PM, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the tip tree got a conflict in > arch/x86/kernel/ptrace.c between commit 91397401bb50 ("ARCH: AUDIT: > audit_syscall_entry() should not require the arch") from the audit tree > and commit

Re: linux-next: manual merge of the tip tree with the audit tree

2014-09-24 Thread Andy Lutomirski
On Tue, Sep 23, 2014 at 10:47 PM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, Today's linux-next merge of the tip tree got a conflict in arch/x86/kernel/ptrace.c between commit 91397401bb50 (ARCH: AUDIT: audit_syscall_entry() should not require the arch) from the audit tree and

Re: linux-next: manual merge of the tip tree with the audit tree

2014-09-24 Thread Andy Lutomirski
On Wed, Sep 24, 2014 at 11:12 AM, Andy Lutomirski l...@amacapital.net wrote: On Tue, Sep 23, 2014 at 10:47 PM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, Today's linux-next merge of the tip tree got a conflict in arch/x86/kernel/ptrace.c between commit 91397401bb50 (ARCH: AUDIT:

linux-next: manual merge of the tip tree with the audit tree

2014-09-23 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the tip tree got a conflict in arch/x86/kernel/ptrace.c between commit 91397401bb50 ("ARCH: AUDIT: audit_syscall_entry() should not require the arch") from the audit tree and commit e0ffbaabc46d ("x86: Split syscall_trace_enter into two phases") from the tip

linux-next: manual merge of the tip tree with the audit tree

2014-09-23 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the tip tree got a conflict in arch/x86/kernel/entry_64.S between commit b4f0d3755c5e ("audit: x86: drop arch from __audit_syscall_entry() interface") from the audit tree and commit 1dcf74f6edfc ("x86_64, entry: Use split-phase syscall_trace_enter for 64-bit

linux-next: manual merge of the tip tree with the audit tree

2014-09-23 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the tip tree got a conflict in arch/x86/kernel/entry_64.S between commit b4f0d3755c5e (audit: x86: drop arch from __audit_syscall_entry() interface) from the audit tree and commit 1dcf74f6edfc (x86_64, entry: Use split-phase syscall_trace_enter for 64-bit

linux-next: manual merge of the tip tree with the audit tree

2014-09-23 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the tip tree got a conflict in arch/x86/kernel/ptrace.c between commit 91397401bb50 (ARCH: AUDIT: audit_syscall_entry() should not require the arch) from the audit tree and commit e0ffbaabc46d (x86: Split syscall_trace_enter into two phases) from the tip tree.