Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753675AbaF0SH7 (ORCPT ); Fri, 27 Jun 2014 14:07:59 -0400 Received: from mail-wg0-f41.google.com ([74.125.82.41]:38513 "EHLO mail-wg0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751496AbaF0SH5 (ORCPT ); Fri, 27 Jun 2014 14:07:57 -0400 Message-ID: <1403892474.5830.41.camel@marge.simpson.net> Subject: Re: Filesystem lockup with CONFIG_PREEMPT_RT From: Mike Galbraith To: Steven Rostedt Cc: Austin Schuh , Thomas Gleixner , Richard Weinberger , LKML , rt-users Date: Fri, 27 Jun 2014 20:07:54 +0200 In-Reply-To: <20140627135415.7246e87e@gandalf.local.home> References: <1403873856.5827.56.camel@marge.simpson.net> <20140627100157.6b0143a5@gandalf.local.home> <1403890493.5830.33.camel@marge.simpson.net> <20140627135415.7246e87e@gandalf.local.home> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2014-06-27 at 13:54 -0400, Steven Rostedt wrote: > On Fri, 27 Jun 2014 19:34:53 +0200 > Mike Galbraith wrote: > > > On Fri, 2014-06-27 at 10:01 -0400, Steven Rostedt wrote: > > > > > This seems like a lot of hacks. > > > > It is exactly that, lacking proper pooper-scooper, show rt kernel how to > > not step in it. > > > > > I'm wondering if it would work if we > > > just have the rt_spin_lock_slowlock not call schedule(), but call > > > __schedule() directly. I mean it would keep with the mainline paradigm > > > as spinlocks don't sleep there, and one going to sleep in the -rt > > > kernel is similar to it being preempted by a very long NMI. > > > > Problem being that we do sleep there, do need wakeup. I have a hack > > that turns them back into spinning locks, but it.. works too :) > > Why do we need the wakeup? the owner of the lock should wake it up > shouldn't it? True, but that can take ages. -Mike -- 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/