All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tyler Hicks <tyhicks@canonical.com>
To: jmorris@namei.org
Cc: David Miller <davem@davemloft.net>,
	linux-security-module@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, serge.hallyn@canonical.com
Subject: Re: [PATCH 0/2] Quiet noisy LSM denial when accessing net sysctl
Date: Tue, 17 May 2016 09:13:47 -0500	[thread overview]
Message-ID: <573B271B.30202@canonical.com> (raw)
In-Reply-To: <20160508.235620.333454221783238471.davem@davemloft.net>


[-- Attachment #1.1: Type: text/plain, Size: 427 bytes --]

On 05/08/2016 10:56 PM, David Miller wrote:
> From: Tyler Hicks <tyhicks@canonical.com>
> Date: Fri,  6 May 2016 18:04:12 -0500
> 
>> This pair of patches does away with what I believe is a useless denial
>> audit message when a privileged process initially accesses a net sysctl.
> 
> The LSM folks can apply this if they agree with you.

Hi James - Could you pick up these two bug fix patches? Thanks!

Tyler



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-05-17 14:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-06 23:04 [PATCH 0/2] Quiet noisy LSM denial when accessing net sysctl Tyler Hicks
2016-05-06 23:04 ` [PATCH 1/2] kernel: Add noaudit variant of ns_capable() Tyler Hicks
2016-05-09  4:23   ` Serge Hallyn
2016-05-06 23:04 ` [PATCH 2/2] net: Use ns_capable_noaudit() when determining net sysctl permissions Tyler Hicks
2016-05-09  4:24   ` Serge Hallyn
2016-05-09  3:56 ` [PATCH 0/2] Quiet noisy LSM denial when accessing net sysctl David Miller
2016-05-17 14:13   ` Tyler Hicks [this message]
2016-06-02 16:30     ` Tyler Hicks
2016-06-03  1:00       ` James Morris

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=573B271B.30202@canonical.com \
    --to=tyhicks@canonical.com \
    --cc=davem@davemloft.net \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=serge.hallyn@canonical.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.