From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id EE878211546EC for ; Fri, 21 Sep 2018 16:07:18 -0700 (PDT) From: David Howells In-Reply-To: <153549644916.4089.12258485183075906901.stgit@djiang5-desk3.ch.intel.com> References: <153549644916.4089.12258485183075906901.stgit@djiang5-desk3.ch.intel.com> <153549632073.4089.3609134467249378610.stgit@djiang5-desk3.ch.intel.com> Subject: Re: [PATCH v8 02/12] libnvdimm: create keyring to store security keys MIME-Version: 1.0 Content-ID: <16646.1537571236.1@warthog.procyon.org.uk> Date: Sat, 22 Sep 2018 00:07:16 +0100 Message-ID: <16648.1537571236@warthog.procyon.org.uk> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Dave Jiang Cc: alison.schofield@intel.com, keescook@chromium.org, linux-nvdimm@lists.01.org, ebiggers3@gmail.com, dhowells@redhat.com, keyrings@vger.kernel.org List-ID: Dave Jiang wrote: > +static void nvdimm_unregister_keyring(void) > +{ > + key_revoke(nvdimm_keyring); > +} You need key_put() as well otherwise you'll leak a ref. David _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm