From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S935618AbcCQKW6 (ORCPT <rfc822;w@1wt.eu>);
	Thu, 17 Mar 2016 06:22:58 -0400
Received: from www.linutronix.de ([62.245.132.108]:59426 "EHLO
	Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S935295AbcCQKWx (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Thu, 17 Mar 2016 06:22:53 -0400
Date: Thu, 17 Mar 2016 11:21:24 +0100 (CET)
From: Thomas Gleixner <tglx@linutronix.de>
To: Peter Zijlstra <peterz@infradead.org>
cc: Xiong Zhou <jencce.kernel@gmail.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>,
        Andreas Herrmann <aherrmann@suse.com>
Subject: Re: 4.5.0+ panic when setup loop device
In-Reply-To: <20160317095220.GO6344@twins.programming.kicks-ass.net>
Message-ID: <alpine.DEB.2.11.1603171119060.3978@nanos>
References: <CADJHv_ty-8OsX3YKKYg4vtzcL-Hmag3rtjObbcgFLE-KLt1M7g@mail.gmail.com> <alpine.DEB.2.11.1603161624280.3978@nanos> <CADJHv_s1cM=NxkCSHEm_1MctDYJUkDtutLB=aFtx9rB4a3FZdw@mail.gmail.com> <20160317095220.GO6344@twins.programming.kicks-ass.net>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Linutronix-Spam-Score: -1.0
X-Linutronix-Spam-Level: -
X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required,  ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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.

Thanks,

	tglx