Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp576276ybx; Wed, 30 Oct 2019 01:19:33 -0700 (PDT) X-Google-Smtp-Source: APXvYqznS/NR2O/qKILXKFhpllnqKWsI0tHmlKNXm8Z9XxeEGsHx63/2V6mVQ6Sg68vDedvpWNWu X-Received: by 2002:a17:906:318e:: with SMTP id 14mr7726727ejy.5.1572423573566; Wed, 30 Oct 2019 01:19:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1572423573; cv=none; d=google.com; s=arc-20160816; b=nWYPzvjkbCZTdmVBsynLh0qeoI+MfDlR8BA0ISYPhGrudx8nG//PpGQd1bTvj3rXLA anolorUodVadtdLjzyUp5fnVlXL5aN1Ubgf4WLaar+6ipb7RMjxdtCnUrlKFJKiv1O1y aaaSL5O6chwOw0rrXhGqejDXPkn10I8NWxzaJXTdccbnK/0CgSziFvLPOGWLeeTcD+XQ Yl3KF/5d+shLpRv/gKjU07h/Z2CRWPSaXQLDtD5F/vOKlRDc8Bj5gINP/Hts6uzulQ3E nQqs/B/3zFoazsV4MB626n0JhaH9cMDMoEpuKmdVb6K9jgF0cP2IXsHS+2WtwIUWdsnX FKbw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-disposition :content-transfer-encoding:mime-version:in-reply-to:references :subject:cc:to:from:date:message-id; bh=opmP24rXTJ8FK7faJwmr3lCe2eSn6tenEwisj1NLcuk=; b=C9AmUgLZlI2G6nW1YOEdxVPTTbeLLkx1edPGCe0NWd6A9yt89GexIvnHce3u63pOy/ IM6Yob5EjdLQipydFufItm1hdMqu2Hoqaoj3DxnLvSst0jwpd4Bn1jj9B2WgQdfdKkNJ IO9cgux1J+PrYGJXK3tEvUyAp/sSSbhHuQqZeVGYpghjqbSPvFDpR1LCXZ8/g8yApk75 TZyO+C50d7U115OcofT5LMUtpWzeed/Tp24fzwGdxfHq1QAYYyrQWLBTWvc8Qm6k8pvJ 9DAOQdNNLp7g1RqRt0mP/KjnzF9hB3ox8W1g3TsnYZIxe5eZLCQ+v5DUOH2aaw6jKL7p e5WA== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r4si750356ejz.77.2019.10.30.01.19.10; Wed, 30 Oct 2019 01:19:33 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726322AbfJ3IQj convert rfc822-to-8bit (ORCPT + 99 others); Wed, 30 Oct 2019 04:16:39 -0400 Received: from mx2.uni-regensburg.de ([194.94.157.147]:39476 "EHLO mx2.uni-regensburg.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725822AbfJ3IQi (ORCPT ); Wed, 30 Oct 2019 04:16:38 -0400 Received: from mx2.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 0671C6000059; Wed, 30 Oct 2019 09:16:36 +0100 (CET) Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx2.uni-regensburg.de (Postfix) with ESMTP id EB5EE6000051; Wed, 30 Oct 2019 09:16:35 +0100 (CET) Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Wed, 30 Oct 2019 09:16:35 +0100 Message-Id: <5DB946E1020000A100034B9C@gwsmtp.uni-regensburg.de> X-Mailer: Novell GroupWise Internet Agent 18.1.1 Date: Wed, 30 Oct 2019 09:16:33 +0100 From: "Ulrich Windl" To: "open-iscsi" , , , "Chris Leech" , "Lee Duncan" , , Cc: , Subject: Antw: [PATCH v2] scsi: avoid potential deadloop in iscsi_if_rx func References: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8BIT Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >>> "wubo (T)" schrieb am 30.10.2019 um 08:56 in Nachricht : > From: Bo Wu ... > + if (--retries < 0) { > + printk(KERN_ERR "Send reply failed too many times. " > + "Max supported retries %u\n", ISCSI_SEND_MAX_ALLOWED); Just for "personal taste": Why not simplify the message to:? + printk(KERN_ERR "Send reply failed too many times (%u)\n", ISCSI_SEND_MAX_ALLOWED); > + break; > + } > + Maybe place the number after "many" as an alternative. I think as the message is expected to be rare, a short variant is justified. Also one could discuss wether the problem that originates "from external" should be KERN_ERR, or maybe just a warning, because the kernel itself can do little against that problem, and it's not a "kernel error" after all ;-) Regards, Ulrich