From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751001AbdBFRrs (ORCPT ); Mon, 6 Feb 2017 12:47:48 -0500 Received: from mx2.suse.de ([195.135.220.15]:58643 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751372AbdBFRrr (ORCPT ); Mon, 6 Feb 2017 12:47:47 -0500 Date: Mon, 6 Feb 2017 18:47:43 +0100 From: "Luis R. Rodriguez" To: Borislav Petkov Cc: Guenter Roeck , "Luis R. Rodriguez" , Stephen Rothwell , Mark Brown , Fengguang Wu , "linux-kernel@vger.kernel.org" , X86 ML , Andy Lutomirski Subject: Re: Regression on next-20170203 spi/for-next 3f87493930a0f qemu on x86_64 Message-ID: <20170206174743.GA24047@wotan.suse.de> References: <99a373c8-2ae2-677a-4053-4b3f7273635f@roeck-us.net> <20170205103325.w5qnzmzveowwkbks@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170205103325.w5qnzmzveowwkbks@pd.tnic> User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Feb 05, 2017 at 11:33:25AM +0100, Borislav Petkov wrote: > On Sat, Feb 04, 2017 at 05:22:55PM -0800, Guenter Roeck wrote: > > Upstream (v4.10-rc6-193-ga572a1b99948), the same command yields no error at all: > > That's because you tested Linus' merge commit of the branch which fixed that :-) > > IOW, the fix should be: > > aaaec6fc7554 ("x86/irq: Make irq activate operations symmetric") > > It is on its way to stable too, as we speak. I've taken this patch and applied it on top of next-20170203 and confirm it fixes the regression. I've also tested next-20170206 which has the fix and confirm that boots as well. Do we have any test units which can kick off regularly to test against such type of regression in the future or is it not worth it? Thanks Boris! Luis