Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759937AbaGCXIf (ORCPT ); Thu, 3 Jul 2014 19:08:35 -0400 Received: from mail-ig0-f173.google.com ([209.85.213.173]:41972 "EHLO mail-ig0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755997AbaGCXIc (ORCPT ); Thu, 3 Jul 2014 19:08:32 -0400 MIME-Version: 1.0 In-Reply-To: References: From: Austin Schuh Date: Thu, 3 Jul 2014 16:08:11 -0700 Message-ID: Subject: Re: Filesystem lockup with CONFIG_PREEMPT_RT To: Thomas Gleixner Cc: Richard Weinberger , Mike Galbraith , LKML , rt-users , Steven Rostedt Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 1, 2014 at 12:32 PM, Austin Schuh wrote: > On Mon, Jun 30, 2014 at 8:01 PM, Austin Schuh wrote: >> On Fri, Jun 27, 2014 at 7:24 AM, Thomas Gleixner wrote: >>> Completely untested patch below. I've tested it and looked it over now, and feel pretty confident in the patch. Thanks Thomas! I've been running this fix with my extra lock steps for a couple days now on 3 machines, and haven't seen any issues. On each of the machines, I've got a CAN card generating about 1 CPU worth of load from interrupts, and the rest of the cores are tied up putting work on the work queues with the killer_module. What next? Austin -- 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/