public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Waiman Long <Waiman.Long@hp.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	USB list <linux-usb@vger.kernel.org>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: Linux 3.16-rc6
Date: Thu, 24 Jul 2014 14:25:13 +0200	[thread overview]
Message-ID: <20140724122513.GM19239@pd.tnic> (raw)
In-Reply-To: <20140724084126.GB19239@pd.tnic>

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.
--

  reply	other threads:[~2014-07-24 12:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-21  4:22 Linux 3.16-rc6 Linus Torvalds
2014-07-23  9:53 ` Borislav Petkov
2014-07-24  0:37   ` Linus Torvalds
2014-07-24  1:53     ` David Rientjes
2014-07-24  6:43     ` Peter Zijlstra
2014-07-24  8:41       ` Borislav Petkov
2014-07-24 12:25         ` Borislav Petkov [this message]
2014-07-24 12:58           ` Peter Zijlstra
2014-07-24 16:34             ` Borislav Petkov
2014-07-24 18:18             ` Linus Torvalds
2014-07-24 18:36               ` Peter Zijlstra
2014-07-24 20:38                 ` Waiman Long
2014-07-24 21:45                   ` Borislav Petkov
2014-07-25 17:23                     ` Waiman Long
2014-07-24 22:06                   ` John Stoffel
2014-07-25 16:10                   ` Peter Zijlstra
2014-07-28 16:37                     ` Waiman Long
2014-07-28 16:42                       ` Peter Zijlstra

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140724122513.GM19239@pd.tnic \
    --to=bp@alien8.de \
    --cc=Waiman.Long@hp.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox