All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Paul Moore <paul@paul-moore.com>
Cc: Andi Kleen <andi@firstfloor.org>, Eric Paris <eparis@redhat.com>,
	linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] Don't audit SECCOMP_KILL/RET_ERRNO when syscall auditing is disabled
Date: Sat, 9 Apr 2016 19:41:53 -0700	[thread overview]
Message-ID: <20160410024152.GG9407@two.firstfloor.org> (raw)
In-Reply-To: <CAHC9VhSewhy7CdoPVbekMWaftEpAr1o3_JsuUSHoFP3XUGU9pw@mail.gmail.com>

> What kernel version are you using?  I believe we fixed that in Linux
> 4.5 with the following:

This is 4.6-rc2.
> 
>   commit 96368701e1c89057bbf39222e965161c68a85b4b
>   From: Paul Moore <pmoore@redhat.com>
>   Date: Wed, 13 Jan 2016 10:18:55 -0400 (09:18 -0500)
> 
>   audit: force seccomp event logging to honor the audit_enabled flag

No you didn't fix it because audit_enabled is always enabled by systemd
for user space auditing, see the original description of my patch.

-Andi

  reply	other threads:[~2016-04-10  2:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-09 15:07 [PATCH] Don't audit SECCOMP_KILL/RET_ERRNO when syscall auditing is disabled Andi Kleen
2016-04-10  0:56 ` Paul Moore
2016-04-10  2:41   ` Andi Kleen [this message]
2016-04-10 22:17     ` Paul Moore
2016-04-10 22:17       ` Paul Moore
2016-04-10 22:31       ` Andi Kleen
2016-04-11  2:30         ` Paul Moore
2016-04-11  4:07           ` Andi Kleen
2016-04-11 13:23             ` Paul Moore
2016-04-11 13:23               ` Paul Moore
2016-04-12 20:34         ` Richard Guy Briggs
2016-04-12 20:34           ` Richard Guy Briggs

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=20160410024152.GG9407@two.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=ak@linux.intel.com \
    --cc=eparis@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@paul-moore.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.