Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758839AbaGXMZU (ORCPT ); Thu, 24 Jul 2014 08:25:20 -0400 Received: from mail.skyhub.de ([78.46.96.112]:40947 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756834AbaGXMZR (ORCPT ); Thu, 24 Jul 2014 08:25:17 -0400 Date: Thu, 24 Jul 2014 14:25:13 +0200 From: Borislav Petkov To: Waiman Long Cc: Peter Zijlstra , Linus Torvalds , Ingo Molnar , Linux Kernel Mailing List , USB list , "linux-input@vger.kernel.org" Subject: Re: Linux 3.16-rc6 Message-ID: <20140724122513.GM19239@pd.tnic> References: <20140723095327.GA23131@pd.tnic> <20140724064353.GW9918@twins.programming.kicks-ass.net> <20140724084126.GB19239@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20140724084126.GB19239@pd.tnic> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 24, 2014 at 10:41:27AM +0200, Borislav Petkov wrote: > you can easily reproduce by booting a kvm guest with rc6 + tip/master. Right, so reverting 586fefe5bbdc ("locking/selftest: Support queued rwlock") e0645a111cb4 ("locking/lockdep: Restrict the use of recursive read_lock() with qrwlock") from the top of tip/locking/core seems to fix the issue, with the kvm guests at least. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/