Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp2600246rwb; Mon, 19 Sep 2022 07:22:41 -0700 (PDT) X-Google-Smtp-Source: AMsMyM78W07ztDb6692p3Bwfyo3Cke6Wlrl1dUR5uH7LttDP+J7/QoaGWYgM+EhbJTLqOErWKNJO X-Received: by 2002:a17:903:1249:b0:178:639a:1ab1 with SMTP id u9-20020a170903124900b00178639a1ab1mr29431plh.64.1663597361161; Mon, 19 Sep 2022 07:22:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1663597361; cv=none; d=google.com; s=arc-20160816; b=HrXn2O4/ELmjnnVizYgz+2ywVDHmFCCjSOjEtSmv8UhTOniemmi9i6B65Y4xJWB4vg mGSaK+ODgHSRLQtd46Q/1w4X7/w+kgBSo/CvGUe7Bp6FgkueSuTvcUi3A1Pu0S9EuM5g FjHFAgf+qHStryvPIhxHfJw70rf/OLz25QJHebGzt2808wBCrRBC+o7tigGQund/Y8MF 6oEOSSDOAfEDuv9byBwgXpqfMwmCXlVbGjISS+KjTZY5iKECTu31YC6FMxNIeRYDzqA6 aC+sE9YbXMFXdDt1LCDl/fatpoDDD+paC87ZVdFKlGm1IO0xfhggLhP8QYsAODMVW7eH RDxQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=84YAZ5utnAxTlVvwciQRKoFCqoxTT9t5uk+86ESmeNU=; b=F1knAoLmu9Hsd/NX4XyBBXzAM1lIyJ9+5SCQ/fv9Qh9y4/TZbv65cqZPQeX2iRdx1Y QdIRtGrG0Ktqua3rcli/QhHsGtI53iKC9ABHYknrUdlLEMifthhcKHGtErSO++7gpUif lxFg3hg4s2cjpLayw3tPKHkRveNYaYiR0+I7mO6lsvRXWRVBuR6bnu1wGYwCPU6AZHDl yG44/mwpspUBP3xRTMVS7EafazAwLtCZI6F7Q4us4ZIBxoJRrInKTxJq5fSvty3IZShn 302RIP9VIGgHehh8c03E/gBkse9Z7Ijx4uy0jG3RxiAGL3TPIkfNNnpbjl7tmuC9TNDn +OQw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=Gdbi9dFN; 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 s4-20020a170903214400b00176e34ab913si25307909ple.59.2022.09.19.07.22.29; Mon, 19 Sep 2022 07:22:41 -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=Gdbi9dFN; 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 S231153AbiISNrd (ORCPT + 99 others); Mon, 19 Sep 2022 09:47:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56314 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230513AbiISNrP (ORCPT ); Mon, 19 Sep 2022 09:47:15 -0400 Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9D6A330543; Mon, 19 Sep 2022 06:46:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1663595211; x=1695131211; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=YKEKcFYIu6qm0K8+4BMwEimDqvC6SyGiwhDXIYY2JLQ=; b=Gdbi9dFNYCD5ubNxQbLpXkhBQ4pyXQla1RDOaZZRPubxtTkiwIK7j/uY r38sa9Lbyq587Af9GSMzxdUmWzkTz8O4DAmnHz2lTu7WHfdRgTvhvlH5k XsTrnSkCC/CSsxaFfLdoaxE8wMqJW4sCEy2p6kM+LAufO9SLEmULkQqFQ UXwxoeH7SbhvT/AcwT2DslMvvcNqFNejycbnTQyW2TYiUEzGDFy+AM9kj /B6wIyS1Z95jnpv8d2fyj9PSdaAlsf+2/1bNiIDJCcZI7IhrcGVF6Le6K Si8dzqGewEE4qS9HVCE+VC3xn5RugU/Xr0cT/BKHiCrUXvyjyVPRSpqTF A==; X-IronPort-AV: E=McAfee;i="6500,9779,10475"; a="286446956" X-IronPort-AV: E=Sophos;i="5.93,327,1654585200"; d="scan'208";a="286446956" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Sep 2022 06:46:40 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.93,327,1654585200"; d="scan'208";a="569657380" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga003.jf.intel.com with ESMTP; 19 Sep 2022 06:46:38 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1oaH6b-004ZdE-0u; Mon, 19 Sep 2022 16:46:37 +0300 Date: Mon, 19 Sep 2022 16:46:37 +0300 From: Andy Shevchenko To: Lennert Buytenhek Cc: Ilpo =?iso-8859-1?Q?J=E4rvinen?= , Greg Kroah-Hartman , Jiri Slaby , linux-serial , LKML Subject: Re: I/O page faults from 8250_mid PCIe UART after TIOCVHANGUP Message-ID: References: <7fd034a9-c1e1-2dca-693b-129c9d2649@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Spam-Status: No, score=-4.3 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE 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 Fri, Sep 16, 2022 at 02:47:08PM +0300, Lennert Buytenhek wrote: > On Thu, Sep 15, 2022 at 07:27:45PM +0300, Ilpo J?rvinen wrote: ... > Thanks for the fix! > > > [...] I'm far from sure if it's the > > best fix though as I don't fully understand what causes the faults during > > the THRE tests because the port->irq is disabled by the THRE test block. > > If the IRQ hasn't been set up yet, the UART will have zeroes in its MSI > address/data registers. Disabling the IRQ at the interrupt controller > won't stop the UART from performing a DMA write to the address programmed > in its MSI address register (zero) when it wants to signal an interrupt. > > (These UARTs (in Ice Lake-D) implement PCI 2.1 style MSI without masking > capability, so there is no way to mask the interrupt at the source PCI > function level, except disabling the MSI capability entirely, but that > would cause it to fall back to INTx# assertion, and the PCI specification > prohibits disabling the MSI capability as a way to mask a function's > interrupt service request.) This sounds to me like a good part to be injected into commit message of the proposed fix. -- With Best Regards, Andy Shevchenko