From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: [PATCH] scsi_error thread exits in TASK_INTERRUPTIBLE state. Date: Wed, 19 Oct 2005 13:56:53 +0200 Message-ID: <20051019115653.GA2127@elte.hu> References: <5bdc1c8b0510181402o2d9badb0sd18012cf7ff2a329@mail.gmail.com> <1129693423.8910.54.camel@mindpipe> <1129695564.8910.64.camel@mindpipe> <20051019113131.GA30553@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mx2.mail.elte.hu ([157.181.151.9]:32472 "EHLO mx2.mail.elte.hu") by vger.kernel.org with ESMTP id S1750827AbVJSL45 (ORCPT ); Wed, 19 Oct 2005 07:56:57 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Steven Rostedt Cc: Christoph Hellwig , Lee Revell , Mark Knecht , linux-kernel@vger.kernel.org, rmk@arm.linux.org.uk, Linus Torvalds , Andrew Morton , andmike@us.ibm.com, linux-scsi@vger.kernel.org * Steven Rostedt wrote: > On Wed, 19 Oct 2005, Christoph Hellwig wrote: > > > > + /* > > > + * There's a good chance that the loop will exit in the > > > + * TASK_INTERRUPTIBLE state. > > > + */ > > > + __set_current_state(TASK_RUNNING); > > > > no need to comment the obvious. > > So, should I resend the patch without the comment? i guess so. OTOH, if it was so obvious, why did it stay unfixed for so long ;-) Ingo