Received: by 10.213.65.68 with SMTP id h4csp3134901imn; Mon, 9 Apr 2018 15:06:49 -0700 (PDT) X-Google-Smtp-Source: AIpwx49pnXeDdDqEVeBCJNC78Vs3PNJbu6miR16+w08rqr4HU78y6U8Bx4q/E1Lr76ZNs9eTQgWs X-Received: by 10.99.181.89 with SMTP id u25mr5191890pgo.319.1523311609146; Mon, 09 Apr 2018 15:06:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523311609; cv=none; d=google.com; s=arc-20160816; b=w5iIFyzhx7xY34e/v9wurk/xui7lqYvA+2t/5I6trQvJcyZU9TuxMYCc4xSlEs/pce KT/JVkUdGjIG0LHwFjJVY7VvvOpRUxrH+Xvbxrwk2zCPrXI185CkS0Uy0Q2od10b4TyA rhIYHf2ddpD30bYjcLsl1+7K47JolFKxtpBqiMS2THiG40u14qAmhkoux3y17IeyMzzr 7VvCIdfgtqCBlRfLfNyHhIPZ9y2yxCaVBkK8lagGbgz3wCUbD/EV09r3v0Mi/v0r7u0t kMJsdL9fQW5zGZwwP1Yf7CCn7Crr09qUJt7/Q6sDj55UpzwO/S5jo+1ijnKt+AB313Uf +3zQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:content-transfer-encoding :mime-version:references:in-reply-to:date:cc:to:from:subject :arc-authentication-results; bh=Xl5PRjVC1557XezEZ4hZDHz7IMVUKTrItC9KTs/tXEo=; b=0WPzjP00f4rgTGszmzed5pZT6CDivRKzWDoIdWsh5OvjevsULj9eLAIR3mmFELo4aR 7HZNAEOkiNeJzmV2a5XfwFYyfQuUumsfu6ra0rwOgvOtPMomKO9PIZAQdYKGJCJUCVYU UNv7RSKHxl80fruy7x+fgm1mB46oge51kCh3BH4YSBHs6ep8+aSRhMxHb8CzVnr/sfbC xLo/u7xgo3Ku9fFDFzyuLQbrNzAIibXJpfdx6u7Gl0QdH+2tDckBhHmP1G0YySjOHq80 MY/zEpvoyA3HkOGo8QvVS36cEl6vhH091gEpjbCg3wvibe7c9kHPKvIRnWEfgNjydSZy nQMw== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o32-v6si1165143pld.435.2018.04.09.15.06.11; Mon, 09 Apr 2018 15:06:49 -0700 (PDT) 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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752630AbeDIOaJ (ORCPT + 99 others); Mon, 9 Apr 2018 10:30:09 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:37276 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752588AbeDIOaH (ORCPT ); Mon, 9 Apr 2018 10:30:07 -0400 Received: from pps.filterd (m0098414.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w39EL1MV087881 for ; Mon, 9 Apr 2018 10:30:07 -0400 Received: from e06smtp10.uk.ibm.com (e06smtp10.uk.ibm.com [195.75.94.106]) by mx0b-001b2d01.pphosted.com with ESMTP id 2h870bs89q-1 (version=TLSv1.2 cipher=AES256-SHA256 bits=256 verify=NOT) for ; Mon, 09 Apr 2018 10:30:06 -0400 Received: from localhost by e06smtp10.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Mon, 9 Apr 2018 15:30:03 +0100 Received: from b06cxnps3075.portsmouth.uk.ibm.com (9.149.109.195) by e06smtp10.uk.ibm.com (192.168.101.140) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Mon, 9 Apr 2018 15:30:00 +0100 Received: from d06av23.portsmouth.uk.ibm.com (d06av23.portsmouth.uk.ibm.com [9.149.105.59]) by b06cxnps3075.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id w39EU0be14614896; Mon, 9 Apr 2018 14:30:00 GMT Received: from d06av23.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id C786CA405D; Mon, 9 Apr 2018 15:22:19 +0100 (BST) Received: from d06av23.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id B61CCA404D; Mon, 9 Apr 2018 15:22:18 +0100 (BST) Received: from localhost.localdomain (unknown [9.80.101.38]) by d06av23.portsmouth.uk.ibm.com (Postfix) with ESMTP; Mon, 9 Apr 2018 15:22:18 +0100 (BST) Subject: Re: [PATCH] tpm: moves the delay_msec increment after sleep in tpm_transmit() From: Mimi Zohar To: Jarkko Sakkinen , Nayna Jain Cc: linux-integrity@vger.kernel.org, linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, peterhuewe@gmx.de, tpmdd@selhorst.net, jgunthorpe@obsidianresearch.com Date: Mon, 09 Apr 2018 10:29:58 -0400 In-Reply-To: <20180407103610.GA22542@linux.intel.com> References: <20180402162006.5030-1-nayna@linux.vnet.ibm.com> <20180405101210.GA21636@linux.intel.com> <95af65a1-e618-5cdf-fb81-56434f1aa973@linux.vnet.ibm.com> <20180407103610.GA22542@linux.intel.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.20.5 (3.20.5-1.fc24) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 x-cbid: 18040914-0040-0000-0000-0000042C2AE6 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18040914-0041-0000-0000-000026303623 Message-Id: <1523284198.16421.196.camel@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-04-09_06:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1709140000 definitions=main-1804090152 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 2018-04-07 at 13:36 +0300, Jarkko Sakkinen wrote: > On Fri, Apr 06, 2018 at 02:03:37PM +0530, Nayna Jain wrote: > > On 04/05/2018 03:42 PM, Jarkko Sakkinen wrote: > > > On Mon, Apr 02, 2018 at 09:50:06PM +0530, Nayna Jain wrote: > > > > Commit e2fb992d82c6 ("tpm: add retry logic") introduced a new loop to > > > > handle the TPM2_RC_RETRY error. The loop retries the command after > > > > sleeping for the specified time, which is incremented exponentially in > > > > every iteration. This patch fixes the initial sleep to be the default > > > > sleep time. > > > I think I understand the code change but do not understand what the > > > long description. > > > > It tells that the first sleep is delay_msec * 2 and not delay_msec. > > So the problem is that the loop doubles the time before sleeping > for the first time. This is missing from the description. Please > refine it in some way. Sure, how about replacing the last line of the patch description with: Unfortunately, the loop doubles the time before sleeping, causing the initial sleep to be doubled. This patch fixes the initial sleep time. If this change is acceptable, do you want to make the change or should Nayna repost the patch? thanks, Mimi