Received: by 2002:a05:6358:45e:b0:b5:b6eb:e1f9 with SMTP id 30csp2828110rwe; Mon, 29 Aug 2022 00:24:57 -0700 (PDT) X-Google-Smtp-Source: AA6agR6w8+AOVC0ovWJt90v24Rjymn6hSKeZs9QoJgdvAw+yuv6tE8dJO6qx5Nms4jYfCfyEuf7j X-Received: by 2002:a63:2a95:0:b0:41a:27e5:1996 with SMTP id q143-20020a632a95000000b0041a27e51996mr12776635pgq.447.1661757897422; Mon, 29 Aug 2022 00:24:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1661757897; cv=none; d=google.com; s=arc-20160816; b=crcbkMnlHm3lrroi45ABhn+PtEwLV8WEWNzez5/AQ0qbrZeEEgCSFEv1M7gRj0y2ob HQsbsqUEEtLTQ07hHNFxaivPLS9hFa/+yGfAp1dvU1PqarfCJbEc1Wn4XsacBWqKTiKp aSjuiOKaI7JWHu8n+OqeS3t6C3DpYa8NfvZHUP3fy9WoAYgMZWP2MMH2zAKn5e7FMEZC 1MI8pkoZMOzpCJHF3d8K4IQs6WgofJCj5+qzXo8dC/qy6MvKou0LGMEfutWkladYl17r k6wjRaaVd2J1PNUq7kvJHGBFvbBFasWaT0yAaDXY8CqNlN1/jQdLKTJm+rJwwj/8xCfv Ll7g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:message-id:in-reply-to :subject:cc:to:from:date:dkim-signature; bh=fo4/9E7cuPUVykM3VLDBXWlxS4JAXhJ40+mcZTJ9HiQ=; b=YabvbgEgtU1zRQ4Zi03PZYI1tJrN7/nrnwR6qKUn3fpA+MgY/o0+mDM4fxgRIF9+bI lwPqnc/Buq6Csnmi+/t5iSFHBdWQNig2Zt2R9NlAtE7HbZet7eKMeNxjLdo+b6AEztrX NQfF6JJlgPNJexb5j1Mvcu02fL8IALtDEYDFdbS4HE9lm3GDpWj6ws5Q0ULaW5or2Ekv +aqCbnAghImDv9S7SynXbvlJVUu+rWJ+VDWTMy8oWnT9Vi0hv3j1NVI7Zd21wfGtzwNw x8ap5Ia7t+bfHp0BUts3IJ8ob0n5B+FH3RfAZ4ImkzSMu5+2f66crChUGDS0Yr/xK/E3 ZNew== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=DOxvuE8f; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id l24-20020a17090aaa9800b001fd833579aesi5761982pjq.111.2022.08.29.00.24.46; Mon, 29 Aug 2022 00:24:57 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=DOxvuE8f; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229593AbiH2HJe (ORCPT + 99 others); Mon, 29 Aug 2022 03:09:34 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52382 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229457AbiH2HJc (ORCPT ); Mon, 29 Aug 2022 03:09:32 -0400 Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E4ACF4D25B; Mon, 29 Aug 2022 00:09:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1661756971; x=1693292971; h=date:from:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=baQTIOLDQEoqRnoLj/vI0QftoJ6RTiQ+sRuCKDr2yh8=; b=DOxvuE8fBFmAKEWaFQyVQ+Hia82a0kJVjqcDBWfsMfYagQvIgOufnrDY 8iayJkIboMiFC1cxhdnOeZkyDDHNlUGEhQ7EDIJ4fEfqHh/bRzziDgw8P Cz88ohVthVjTvsDM8V6w1qL7cyoVmZLhMbY+ArTkeYM8QgX/YmS/rlbkc Ceb/Xw2ppaDirXsy5NZ68gS0crwIIr3BlqNJlgdvBd8G/l8odj8b+hbcq f7mkGd3To7EWUEj98pkVQQZvoXpF6lDYh1/Ti1eTTJZF7fwc38Ujjh26w xPHJ0qBouIO6yF5mQzte96B3GppSWv62fBQXe6WWGAjwF0n0/0tCqEZIz Q==; X-IronPort-AV: E=McAfee;i="6500,9779,10453"; a="277841578" X-IronPort-AV: E=Sophos;i="5.93,272,1654585200"; d="scan'208";a="277841578" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Aug 2022 00:09:30 -0700 X-IronPort-AV: E=Sophos;i="5.93,272,1654585200"; d="scan'208";a="672268649" Received: from kvehmane-mobl1.ger.corp.intel.com ([10.251.220.41]) by fmsmga008-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Aug 2022 00:09:28 -0700 Date: Mon, 29 Aug 2022 10:09:25 +0300 (EEST) From: =?ISO-8859-15?Q?Ilpo_J=E4rvinen?= To: Li Zhong cc: Andy Shevchenko , "open list:SERIAL DRIVERS" , Linux Kernel Mailing List , Greg Kroah-Hartman , Jiri Slaby Subject: Re: [PATCH v2] drivers/tty/serial: check the return value of uart_port_check() In-Reply-To: Message-ID: <2033d06d-10a4-5a57-d650-7541c39990ee@linux.intel.com> References: <20220826083612.1699194-1-floridsleeves@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,SPF_HELO_NONE,SPF_NONE, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 28 Aug 2022, Li Zhong wrote: > On Fri, Aug 26, 2022 at 9:01 AM Andy Shevchenko > wrote: > > > > On Fri, Aug 26, 2022 at 11:38 AM Li Zhong wrote: > > > > > > uart_port_check() will return NULL pointer when state->uart_port is > > > NULL. Check the return value before dereference it to avoid > > > null-pointer-dereference error. > > > > Have you taken the locking into consideration? > > If no, please do, if yes, expand your commit message to explain why > > the current locking scheme doesn't prevent an error from happening. > > > > The locking is taken into consideration but these three checks do not need to > unlock in error-handling because unlock() will be called in the callers. Will > add the comment in v2 patch. I think he meant you should indicate why the current locking doesn't cover the case you're fixing, not whether this function should call unlock() or not. -- i.