Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp321917ybl; Thu, 12 Dec 2019 19:08:57 -0800 (PST) X-Google-Smtp-Source: APXvYqy6llHahDRqvga4fKiatIKuaMZpatSAI3K9HUecczdsVJbqwN3x/Ad/NNS7hG56TJZJGbDv X-Received: by 2002:a05:6830:1db3:: with SMTP id z19mr12729653oti.152.1576206536853; Thu, 12 Dec 2019 19:08:56 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1576206536; cv=none; d=google.com; s=arc-20160816; b=Nwiyf7Qrv0xWGlRYdv5PMDA2MTksuYL0t09/LQc+mqc3de2BlLfEV4SCqdUICgUuSU a/HaPUmfc7CmvslRbw8w60HXud9hShAg83EiuXVVbGdhKI6s28G70UN2YPrBn4ppntda eCam0U0L0fDkGAX446UuOAdxFWH9zXLJ7RVrZZQEADV/fmr3Yzcfi7M3bwsO1XbxYl1E LtPaY2ntIZj3q9TVCrOQyJjBbZhu6uX6pTKFy4KAB5+hDwFR/jgocrIO8Pl0kL2605C5 Vbjm3lgRHAHvGa7rQ02GIujERHR2UntqlY6nuXTBI0S84VGxMszg8vd4q7LnvpOW0L7R PO2Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature:dkim-filter; bh=qv+NmmnZ+/n9eF3FzeCcHEgZTGuVHBDcefUGSa3G2Ug=; b=ErFHSOJncSSno46VS31M0UHM11XiXqIKOc/83nkEU9TE+u0XSxHOhtstnhzYf01WGu pAQBm1hhTTZGbewA+KyZiisuz6t9UoPvcUHb4eAneZ7kw9dnBSDw+kXlJfXkin8KTZS+ aN7+C2uvgWtkhXO98Cw09+SVjL3EWF4TBWOdvbAFnHIiZJ2SgM1DxFKirzmKe3H8zZW4 GP1vh4eJaL1mRYVcLJfAc+gsmky53Uu9HOmaWUHm0f1rq6EnLtgfQVbnT/7vMIR4KeO5 qqGPLj8UzUY+AEviQMYR9rAbwwJMlvCtH8pFIbNEwhOlq23WnWq+sHexaI2vb/ipcKPq gjFA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linux.microsoft.com header.s=default header.b=mvV048o5; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linux.microsoft.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k185si1608928oif.81.2019.12.12.19.08.44; Thu, 12 Dec 2019 19:08:56 -0800 (PST) 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; Authentication-Results: mx.google.com; dkim=pass header.i=@linux.microsoft.com header.s=default header.b=mvV048o5; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linux.microsoft.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731797AbfLMC7Q (ORCPT + 99 others); Thu, 12 Dec 2019 21:59:16 -0500 Received: from linux.microsoft.com ([13.77.154.182]:41646 "EHLO linux.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731465AbfLMC7Q (ORCPT ); Thu, 12 Dec 2019 21:59:16 -0500 Received: from [10.137.112.111] (unknown [131.107.147.111]) by linux.microsoft.com (Postfix) with ESMTPSA id 2DA5820B7187; Thu, 12 Dec 2019 18:59:15 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com 2DA5820B7187 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1576205955; bh=qv+NmmnZ+/n9eF3FzeCcHEgZTGuVHBDcefUGSa3G2Ug=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=mvV048o53KZrnKUqBWi40AGMeYEPwiiAx3txKH0je5V8BQHmIW8UQ03ad8Z3hPAAf bUr4X2ZCRYkT0HLu0Ljs7y9O14mIukU7XyaxUCh9MiWMy6feKWF3KGqHWHRevCUYUM IyS/6OHbMg6T3Tsm9ESbrhWes2lpClPsNMtTkyxY= Subject: Re: [PATCH v3 1/2] IMA: Define workqueue for early boot "key" measurements To: Mimi Zohar , linux-integrity@vger.kernel.org Cc: eric.snowberg@oracle.com, dhowells@redhat.com, mathew.j.martineau@linux.intel.com, matthewgarrett@google.com, sashal@kernel.org, jamorris@linux.microsoft.com, linux-kernel@vger.kernel.org, keyrings@vger.kernel.org References: <20191213004250.21132-1-nramas@linux.microsoft.com> <20191213004250.21132-2-nramas@linux.microsoft.com> <1576202134.4579.189.camel@linux.ibm.com> <6e0dad33-66f9-4807-d08d-ff30396cec5e@linux.microsoft.com> <1576204377.4579.206.camel@linux.ibm.com> From: Lakshmi Ramasubramanian Message-ID: Date: Thu, 12 Dec 2019 18:59:39 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.3.0 MIME-Version: 1.0 In-Reply-To: <1576204377.4579.206.camel@linux.ibm.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/12/2019 6:32 PM, Mimi Zohar wrote: >>> >>> Don't you need a test here, before setting ima_process_keys? >>> >>> if (ima_process_keys) >>> return; >>> >>> Mimi >> >> That check is done before the comment - at the start of >> ima_process_queued_keys(). > > The first test prevents taking the mutex unnecessarily. > > Mimi I am trying to understand your concern here. Could you please clarify? => If ima_process_keys is false -> With the mutex held, should check ima_process_keys again before setting? Let's say 2 or more threads are racing in calling ima_process_queued_keys(): The 1st one will set ima_process_keys and process queued keys. The 2nd and subsequent ones - even if they have gone past the initial check, will find an empty list of keys (the list "ima_keys") when they take the mutex. So they'll not process any keys. thanks, -lakshmi