From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753849AbdKXVYd (ORCPT ); Fri, 24 Nov 2017 16:24:33 -0500 Received: from mx1.redhat.com ([209.132.183.28]:53670 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753730AbdKXVYc (ORCPT ); Fri, 24 Nov 2017 16:24:32 -0500 Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <20171120225757.96498-1-ebiggers3@gmail.com> References: <20171120225757.96498-1-ebiggers3@gmail.com> To: Eric Biggers Cc: dhowells@redhat.com, keyrings@vger.kernel.org, linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, Eric Biggers Subject: Re: [PATCH] KEYS: remove unnecessary get/put of explicit dest_keyring MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <5686.1511558670.1@warthog.procyon.org.uk> Date: Fri, 24 Nov 2017 21:24:30 +0000 Message-ID: <5687.1511558670@warthog.procyon.org.uk> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.32]); Fri, 24 Nov 2017 21:24:32 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Eric Biggers wrote: > if (dest_keyring) { > - construct_get_dest_keyring(&dest_keyring); Actually, I think I have the order of these lines inverted. construct_get_dest_keyring() can actually return without setting dest_keyring to anything. This didn't used to be the case, but now that the user-session keyring is made lazily, there's no guaranteed fallback. David