Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 25 Apr 2018 14:48:37 -0400 (EDT)
Message-Id: <20180425.144837.752183283641043903.davem@davemloft.net>
To:     jmorris@namei.org
Cc:     dh.herrmann@gmail.com, linux-kernel@vger.kernel.org,
        paul@paul-moore.com, teg@jklm.no, sds@tycho.nsa.gov,
        selinux@tycho.nsa.gov, linux-security-module@vger.kernel.org,
        eparis@parisplace.org, serge@hallyn.com, netdev@vger.kernel.org
Subject: Re: [PATCH 0/3] Introduce LSM-hook for socketpair(2)
From:   David Miller <davem@davemloft.net>
In-Reply-To: <alpine.LRH.2.21.1804260443110.11568@namei.org>
References: <20180423133015.5455-1-dh.herrmann@gmail.com>
        <alpine.LRH.2.21.1804260443110.11568@namei.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

From: James Morris <jmorris@namei.org>
Date: Thu, 26 Apr 2018 04:44:38 +1000 (AEST)

> On Mon, 23 Apr 2018, David Herrmann wrote:
> 
>> This patch series tries to close this gap and makes both behave the
>> same. A new LSM-hook is added which allows LSMs to cache the correct
>> peer information on newly created socket-pairs.
> 
> Looks okay to me.
> 
> Once it's respun with the Smack backend and maybe the hook name change, 
> I'll merge this unless DaveM wants it to go in via his networking tree.

No, feel free to take it via your tree James.