Linux Security Modules development
 help / color / mirror / Atom feed
From: pablo@netfilter.org (Pablo Neira Ayuso)
To: linux-security-module@vger.kernel.org
Subject: [PATCH security-next 1/2] smack: use pernet operations for hook registration
Date: Fri, 2 Jun 2017 10:33:22 +0200	[thread overview]
Message-ID: <20170602083322.GA2117@salvia> (raw)
In-Reply-To: <0868b816-939b-12d2-c8aa-a5c8677e1cce@schaufler-ca.com>

On Thu, Jun 01, 2017 at 09:44:05AM -0700, Casey Schaufler wrote:
> On 4/21/2017 2:49 AM, Florian Westphal wrote:
> > It will allow us to remove the old netfilter hook api in the near future.
> >
> > Signed-off-by: Florian Westphal <fw@strlen.de>
> 
> I have applied this to git://github.com/cschaufler/smack-next#smack-for-4.13

Thanks Casey.

We're very much looking forward to getting rid of all these
nf_register_hooks() calls all over the tree. This patch helps us going
in that direction.
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-06-02  8:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21  9:49 [PATCH security-next 0/2]: switch selinux and smack to pernet ops Florian Westphal
2017-04-21  9:49 ` [PATCH security-next 1/2] smack: use pernet operations for hook registration Florian Westphal
2017-04-21 16:42   ` Casey Schaufler
2017-04-21 17:57   ` Casey Schaufler
2017-06-01 16:44   ` Casey Schaufler
2017-06-02  8:33     ` Pablo Neira Ayuso [this message]
2017-06-02  8:48       ` Florian Westphal
2017-06-02  9:07         ` Pablo Neira Ayuso
2017-06-02 14:36         ` Paul Moore
2017-04-21  9:49 ` [PATCH security-next 2/2] selinux: " Florian Westphal
2017-04-26 20:46   ` Paul Moore
2017-04-26 20:47     ` Paul Moore
2017-06-02 14:33       ` Paul Moore

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=20170602083322.GA2117@salvia \
    --to=pablo@netfilter.org \
    --cc=linux-security-module@vger.kernel.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