stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: David Drysdale <drysdale@google.com>
Cc: Brian Gerst <brgerst@gmail.com>, Ingo Molnar <mingo@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	AKASHI Takahiro <takahiro.akashi@linaro.org>,
	Richard Guy Briggs <rgb@redhat.com>,
	Eric Paris <eparis@redhat.com>, Paul Moore <paul@paul-moore.com>,
	stable@vger.kernel.org, linux-audit@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] audit,x86: add x32_execve[at] to syscall classification
Date: Fri, 6 Mar 2015 09:45:51 -0800	[thread overview]
Message-ID: <20150306174551.GC3930@kroah.com> (raw)
In-Reply-To: <1425656438-3884-3-git-send-email-drysdale@google.com>

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@google.com>
> ---
>  arch/x86/kernel/audit_64.c | 6 ++++++
>  1 file changed, 6 insertions(+)

<formletter>
Cc: stable <stable@vger.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>

      reply	other threads:[~2015-03-06 17:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-06 15:40 [PATCH 0/2] Update audit syscall classification for execve variants David Drysdale
2015-03-06 15:40 ` [PATCH 1/2] audit: add execveat to syscall classification David Drysdale
2015-03-06 17:45   ` Greg KH
2015-03-06 15:40 ` [PATCH 2/2] audit,x86: add x32_execve[at] " David Drysdale
2015-03-06 17:45   ` Greg KH [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=20150306174551.GC3930@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=brgerst@gmail.com \
    --cc=drysdale@google.com \
    --cc=eparis@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-audit@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=paul@paul-moore.com \
    --cc=rgb@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=takahiro.akashi@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;
as well as URLs for NNTP newsgroup(s).