From: Andrew Morton <akpm@osdl.org>
To: Sukadev Bhattiprolu <sukadev@us.ibm.com>
Cc: achirica@gmail.com, hch@infradead.org, linville@tuxdriver.com,
haveblue@us.ibm.com, serue@us.ibm.com, clr@fr.ibm.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kthread: airo.c
Date: Tue, 25 Jul 2006 23:18:39 -0700 [thread overview]
Message-ID: <20060725231839.6a69a85e.akpm@osdl.org> (raw)
In-Reply-To: <20060724181309.GA23938@us.ibm.com>
On Mon, 24 Jul 2006 11:13:09 -0700
Sukadev Bhattiprolu <sukadev@us.ibm.com> wrote:
> Sukadev Bhattiprolu [sukadev@us.ibm.com] wrote:
>
> | Andrew,
> |
> | Javier Achirica, one of the major contributors to drivers/net/wireless/airo.c
> | took a look at this patch, and doesn't have any problems with it. It doesn't
> | fix any bugs and is just a cleanup, so it certainly isn't a candidate
> | for this mainline cycle
>
> Here is the same patch, merged up to 2.6.18-rc2. Christoph's patch (see
> http://lkml.org/lkml/2006/7/13/332) still applies cleanly on top of this.
>
> -----
> The airo driver is currently caching a pid for later use, but with the
> implementation of containers, pids themselves do not uniquely identify
> a task. The driver is also using kernel_thread() which is deprecated in
> drivers.
>
> This patch essentially replaces the kernel_thread() with kthread_create().
> It also stores the task_struct of the airo_thread rather than its pid.
> Since this introduces a second task_struct in struct airo_info, the patch
> renames airo_info.task to airo_info.list_bss_task.
>
> As an extension of these changes, the patch further:
>
> - replaces kill_proc() with kthread_stop()
> - replaces signal_pending() with kthread_should_stop()
> - removes thread completion synchronisation which is handled by
> kthread_stop().
>
> ..
>
> @@ -1736,9 +1736,9 @@ static int readBSSListRid(struct airo_in
> issuecommand(ai, &cmd, &rsp);
> up(&ai->sem);
> /* Let the command take effect */
> - ai->task = current;
> + ai->list_bss_task = current;
> ssleep(3);
> - ai->task = NULL;
> + ai->list_bss_task = NULL;
This looks a little racy to me. It's relatively benign - a race will cause
us to sleep for too long. But it's easy to fix:
--- a/drivers/net/wireless/airo.c~kthread-airoc-race-fix
+++ a/drivers/net/wireless/airo.c
@@ -1733,10 +1733,10 @@ static int readBSSListRid(struct airo_in
cmd.cmd=CMD_LISTBSS;
if (down_interruptible(&ai->sem))
return -ERESTARTSYS;
+ ai->list_bss_task = current;
issuecommand(ai, &cmd, &rsp);
up(&ai->sem);
/* Let the command take effect */
- ai->list_bss_task = current;
ssleep(3);
ai->list_bss_task = NULL;
}
_
<looks more closely>
Actually, ssleep() ends up doing
while (timeout)
timeout = schedule_timeout_uninterruptible(timeout);
so if the intent of this code is to terminate the sleep early, when the
interrupt has happened then it isn't working right. A fix would be to
convert the ssleep(3) into schedule_timeout_uninterruptible(3 * HZ).
prev parent reply other threads:[~2006-07-26 6:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 20:53 Sukadev Bhattiprolu
2006-07-13 21:28 ` Christoph Hellwig
2006-07-13 23:00 ` Sukadev Bhattiprolu
2006-07-14 14:35 ` John W. Linville
2006-07-24 18:13 ` Sukadev Bhattiprolu
2006-07-26 6:18 ` Andrew Morton [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=20060725231839.6a69a85e.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=achirica@gmail.com \
--cc=clr@fr.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=serue@us.ibm.com \
--cc=sukadev@us.ibm.com \
/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
all inboxes | Powered by JetHome®