Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755427Ab0ASU6c (ORCPT ); Tue, 19 Jan 2010 15:58:32 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755088Ab0ASU6c (ORCPT ); Tue, 19 Jan 2010 15:58:32 -0500 Received: from mgw1.diku.dk ([130.225.96.91]:41181 "EHLO mgw1.diku.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754759Ab0ASU6b (ORCPT ); Tue, 19 Jan 2010 15:58:31 -0500 Date: Tue, 19 Jan 2010 21:58:28 +0100 (CET) From: Julia Lawall To: Steven Rostedt Cc: LKML , kernel-janitors , Peter Zijlstra , Andrew Morton , linux-arch@vger.kernel.org, Greg KH , Andy Whitcroft Subject: Re: Lots of bugs with current->state = TASK_*INTERRUPTIBLE In-Reply-To: <1263932978.31321.53.camel@gandalf.stny.rr.com> Message-ID: References: <1263932978.31321.53.camel@gandalf.stny.rr.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 624 Lines: 16 > Anyway, this looks like a good janitorial work. Anything that assigns > state outside the rq locks to something other than TASK_RUNNING and that > is not before a schedule() (perhaps even those) should be converted to: > > set_current_task(). Does "not before a schedule" mean not before a schedule_timeout as well? Also, I assume you mean set_current_state? julia -- 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/