linux-kernel - Re: [PATCH 2/2] audit,x86: add x32_execve[at] to syscall classification

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20150306174551.GC3930@kroah.com>
Date:	Fri, 6 Mar 2015 09:45:51 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	David Drysdale <drysdale@...gle.com>
Cc:	Brian Gerst <brgerst@...il.com>, Ingo Molnar <mingo@...nel.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	AKASHI Takahiro <takahiro.akashi@...aro.org>,
	Richard Guy Briggs <rgb@...hat.com>,
	Eric Paris <eparis@...hat.com>,
	Paul Moore <paul@...l-moore.com>, stable@...r.kernel.org,
	linux-audit@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] audit,x86: add x32_execve[at] to syscall
 classification

On Fri, Mar 06, 2015 at 03:40:38PM +0000, David Drysdale wrote:
> Treat x32 ABI variants of execve[at] the same as x86_64
> variants.
> 
> Slightly speculative as the audit subsystem doesn't currently
> work with x32 ABI syscalls.  If and when audit+x32 does work,
> this should correctly classify exec calls.
> 
> Signed-off-by: David Drysdale <drysdale@...gle.com>
> ---
>  arch/x86/kernel/audit_64.c | 6 ++++++
>  1 file changed, 6 insertions(+)

<formletter>
Cc: stable <stable@...r.kernel.org>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read Documentation/stable_kernel_rules.txt
for how to do this properly.

</formletter>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/