Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752889AbaGFE4G (ORCPT ); Sun, 6 Jul 2014 00:56:06 -0400 Received: from mail-ie0-f180.google.com ([209.85.223.180]:50210 "EHLO mail-ie0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752547AbaGFE4E (ORCPT ); Sun, 6 Jul 2014 00:56:04 -0400 MIME-Version: 1.0 In-Reply-To: References: From: Austin Schuh Date: Sat, 5 Jul 2014 21:55:42 -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 Sat, Jul 5, 2014 at 1:26 PM, Thomas Gleixner wrote: > On Mon, 30 Jun 2014, Austin Schuh wrote: >> I think I might have an answer for my own question, but I would >> appreciate someone else to double check. If list_empty erroneously >> returns that there is work to do when there isn't work to do, we wake >> up an extra worker which then goes back to sleep. Not a big loss. If >> list_empty erroneously returns that there isn't work to do when there >> is, this should only be because someone is modifying the work list. >> When they finish, as far as I can tell, all callers then check to see >> if a worker needs to be started up, and start one. > > Precisely. A comment there when you put together a polished patch for inclusion would be awesome. I'm assuming that you will put the patch together? -- 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/