Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932719AbaGEU1A (ORCPT ); Sat, 5 Jul 2014 16:27:00 -0400 Received: from www.linutronix.de ([62.245.132.108]:41353 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754400AbaGEU07 (ORCPT ); Sat, 5 Jul 2014 16:26:59 -0400 Date: Sat, 5 Jul 2014 22:26:54 +0200 (CEST) From: Thomas Gleixner To: Austin Schuh cc: Richard Weinberger , Mike Galbraith , LKML , rt-users , Steven Rostedt Subject: Re: Filesystem lockup with CONFIG_PREEMPT_RT In-Reply-To: Message-ID: References: User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. -- 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/