From: Nishanth Aravamudan <nacc@us.ibm.com>
To: kernel-janitors@vger.kernel.org
Subject: [KJ] [PATCH] class/usblp: cleanup usblp_write()
Date: Wed, 03 Nov 2004 17:55:23 +0000 [thread overview]
Message-ID: <20041103175523.GC2163@us.ibm.com> (raw)
In-Reply-To: <20041022225624.GE11126@us.ibm.com>
On Tue, Nov 02, 2004 at 03:04:15PM -0800, Nishanth Aravamudan wrote:
> On Sat, Oct 23, 2004 at 02:20:00AM +0200, Oliver Neukum wrote:
> > Am Samstag, 23. Oktober 2004 00:56 schrieb Nishanth Aravamudan:
> > > + while (timeout) {
> > > if (signal_pending(current)) {
> > > remove_wait_queue(&usblp->wait, &wait);
> > > return writecount ? writecount : -EINTR;
> > > }
> > > - set_current_state(TASK_INTERRUPTIBLE);
> > > - if (timeout && !usblp->wcomplete) {
> > > - timeout = schedule_timeout(timeout);
> > > - } else {
> > > - set_current_state(TASK_RUNNING);
> > > + if (usblp->wcomplete) {
> > > break;
> > > }
> > > + set_current_state(TASK_INTERRUPTIBLE);
> >
> > You can miss a wake up here.
> >
> > > + timeout = schedule_timeout(timeout);
> > > }
> >
> > The order of checking wcomplete and setting the state must be reversed.
>
> OK, thanks for the pointer. Please find the corrected patch below.
Sorry, I missed a reassignment of the state to TASK_RUNNING in this
patch. Thanks, Domen, for cathing this. Please find the (further)
corrected patch below.
Description: The while-loop seemed excessively blocked with
conditionals. By reorganizing the code so timeout is the condition for
the loop and changing the checks within the loop, several lines of code
were removed.
Signed-off-by: Nishanth Aravamudan <nacc@us.ibm.com>
--- 2.6.10-rc1-vanilla/drivers/usb/class/usblp.c 2004-10-30 15:33:37.000000000 -0700
+++ 2.6.10-rc1/drivers/usb/class/usblp.c 2004-11-03 09:54:41.000000000 -0800
@@ -636,19 +636,17 @@ static ssize_t usblp_write(struct file *
timeout = USBLP_WRITE_TIMEOUT;
add_wait_queue(&usblp->wait, &wait);
- while ( 1=1 ) {
-
+ while (timeout) {
if (signal_pending(current)) {
remove_wait_queue(&usblp->wait, &wait);
return writecount ? writecount : -EINTR;
}
set_current_state(TASK_INTERRUPTIBLE);
- if (timeout && !usblp->wcomplete) {
- timeout = schedule_timeout(timeout);
- } else {
+ if (usblp->wcomplete) {
set_current_state(TASK_RUNNING);
break;
}
+ timeout = schedule_timeout(timeout);
}
remove_wait_queue(&usblp->wait, &wait);
}
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
prev parent reply other threads:[~2004-11-03 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 22:56 [KJ] [PATCH] class/usblp: cleanup usblp_write() Nishanth Aravamudan
2004-11-02 23:04 ` Nishanth Aravamudan
2004-11-03 17:55 ` Nishanth Aravamudan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041103175523.GC2163@us.ibm.com \
--to=nacc@us.ibm.com \
--cc=kernel-janitors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.