From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935637AbcCQK0m (ORCPT ); Thu, 17 Mar 2016 06:26:42 -0400 Received: from casper.infradead.org ([85.118.1.10]:56062 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935501AbcCQK0h (ORCPT ); Thu, 17 Mar 2016 06:26:37 -0400 Date: Thu, 17 Mar 2016 11:26:33 +0100 From: Peter Zijlstra To: Thomas Gleixner Cc: Xiong Zhou , "linux-kernel@vger.kernel.org" , Ingo Molnar , Borislav Petkov , Andreas Herrmann Subject: Re: 4.5.0+ panic when setup loop device Message-ID: <20160317102633.GR6344@twins.programming.kicks-ass.net> References: <20160317095220.GO6344@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 17, 2016 at 11:21:24AM +0100, Thomas Gleixner wrote: > On Thu, 17 Mar 2016, Peter Zijlstra wrote: > > > Could you please try? I'm not sure how this would explain your loop > > device bug fail, but it certainly pointed towards broken. > > It definitely does not explain it. The wreckage that topo stuff causes is that > it disables a cpu, but that really is not a reason for block/loop to explode. Right. Sadly I could not reproduce that error on my machine. But we can at least start by fixing the 'obvious' problems and then maybe we get more clues ;-)