From: Willem Riede <osst@riede.org>
To: Nishanth Aravamudan <nacc@us.ibm.com>
Cc: osst-users@lists.sourceforge.net, linux-scsi@vger.kernel.org,
kernel-janitors@lists.osdl.org
Subject: [PATCH] Re: no set_current_state() before schedule_timeout() (OSST)
Date: Tue, 13 Jul 2004 23:07:32 +0000 [thread overview]
Message-ID: <1089760052l.26949l.0l@serve.riede.org> (raw)
In-Reply-To: <40F41EA6.9000900@us.ibm.com> (from nacc@us.ibm.com on Tue, Jul 13, 2004 at 13:40:54 -0400)
On 07/13/2004 01:40:54 PM, Nishanth Aravamudan wrote:
> Hi,
>
> In continuing to replace, where appropriate, code with msleep() calls, I
> ran across the following file(s) / function(s), which do not invoke
> set_current_state() before schedule_timeout(), which causes the latter
> to return immediately:
>
> drivers/scsi/osst.c::osst_reposition_and_retry()
>
> If someone could tell me which state (TASK_INTERRUPTIBLE or
> TASK_UNINTERRUPTIBLE) is desired, I can fix this and perhaps replace the
> calls with msleep().
You're right, there is a set_current_state(TASK_INTERRUPTIBLE) missing.
I don't know why we would want to change to use msleep() though.
Below is the patch to add the missing statement.
James Bottomley, can you apply this patch?
Regards, Willem Riede.
Signed-off-by: Willem Riede <osst@riede.org>
--- linux-2.6.8-rc1/drivers/scsi/osst.c.orig 2004-07-13
18:59:16.026349000 -0400
+++ linux-2.6.8-rc1/drivers/scsi/osst.c 2004-07-13 19:01:58.040719208
-0400
@@ -1555,6 +1555,7 @@
debugging = 0;
}
#endif
+ set_current_state(TASK_INTERRUPTIBLE);
schedule_timeout(HZ / 10);
}
printk(KERN_ERR "%s:E: Failed to find valid tape media\n", name);
next prev parent reply other threads:[~2004-07-13 22:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 17:40 no set_current_state() before schedule_timeout() (OSST) Nishanth Aravamudan
2004-07-13 23:07 ` Willem Riede [this message]
2004-07-13 23:36 ` [Kernel-janitors] [PATCH] " Nish Aravamudan
2004-07-13 23:56 ` Nishanth Aravamudan
2004-07-14 0:45 ` Willem Riede
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=1089760052l.26949l.0l@serve.riede.org \
--to=osst@riede.org \
--cc=kernel-janitors@lists.osdl.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nacc@us.ibm.com \
--cc=osst-users@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox