Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp8668554ybc; Fri, 29 Nov 2019 14:39:24 -0800 (PST) X-Google-Smtp-Source: APXvYqx5k1Kh6YOEhjyyelBzfgZpobm863uEteWmbRxaNqYGlqr6VorBkxKaojgvw8NXLsuFSLn4 X-Received: by 2002:a50:e88a:: with SMTP id f10mr43535904edn.277.1575067163951; Fri, 29 Nov 2019 14:39:23 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575067163; cv=none; d=google.com; s=arc-20160816; b=IOchocfU5wWJa7L4Bq5T4MzMqPZ2A8s4ZEV4rw904KLeAA6sy1SAyJYLf8FGaxt+81 tUXdLy0YU3Dds3CiVGh8wtWIAOq91EBFDwSbevGKzmsUKTStiDaa5MR1KNv88ibENZ4l bttHUmtk5crP8HGXcvD7BttLVGMneXVtAsPGaDxUzQWefkUzNHEGGhPhUOAejs5gZ27M Or0BkRfc+3z8NjweKGQlAeww+/mmL3N+Qe9dXmU3GK1uHEzr1bNqKJYRC+furrIXhGZs T5d7ZijQuo4Azxk9BP3dS6aG4oOZ1WpW5ScAkcDtOFGyWKM1QrLg77b6uVNEXJNxbqnd rK2g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:organization:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=trV4RiYLIB6uGzsI7VceLhjF7iclcHJkCb51r7mukSE=; b=gSTfboiiP8TDwG+1gpNrneCI4h8oHGYNWt24bjeqST2EsaUepoOouXSpP2YMZOgv38 zKo8oLAY6/XuivlJB+UyydCkA/bOkWAD7KWMID5HMIe3o0AWEXzyZ/HCBQRxRXstAm73 SyPz9G/Gjl4J+z24dPEVKFO32MdtiGc9Ab7akYY8kGX4PjS5pJ8QzuFl4qozkDcyJ/Wc IF14rAJYFZg7X2DLHA+PNAdAOtHdvY2C5EddEBtOFYLJjE/vDiOc7CumQtDO40CyIUSi +g5wIFqIYcr8WuCzpBLO3uiZQxjLpAYcuBWcFeS36nr2uQCU9N23smlgq5CHZQSBwnVJ HieQ== 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=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n8si15401869eja.438.2019.11.29.14.38.59; Fri, 29 Nov 2019 14:39:23 -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; 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=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727196AbfK2Whx (ORCPT + 99 others); Fri, 29 Nov 2019 17:37:53 -0500 Received: from mga06.intel.com ([134.134.136.31]:58517 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727073AbfK2Whw (ORCPT ); Fri, 29 Nov 2019 17:37:52 -0500 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Nov 2019 14:37:52 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,259,1571727600"; d="scan'208";a="384188643" Received: from gamanzi-mobl4.ger.corp.intel.com (HELO localhost) ([10.252.3.126]) by orsmga005.jf.intel.com with ESMTP; 29 Nov 2019 14:37:49 -0800 Date: Sat, 30 Nov 2019 00:37:48 +0200 From: Jarkko Sakkinen To: Stefan Berger Cc: linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org, linux-security-module@vger.kernel.org, Stefan Berger Subject: Re: [PATCH 0/2] Revert patches fixing probing of interrupts Message-ID: <20191129223418.GA15726@linux.intel.com> References: <20191126131753.3424363-1-stefanb@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191126131753.3424363-1-stefanb@linux.vnet.ibm.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 26, 2019 at 08:17:51AM -0500, Stefan Berger wrote: > From: Stefan Berger > > Revert the patches that were fixing the probing of interrupts due > to reports of interrupt stroms on some systems Can you explain how reverting is going to fix the issue? This is wrong way to move forward. The root cause must be identified first and then decide actions like always in any situation. /Jarkko