lkml.org 
[lkml]   [2005]   [Oct]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCH] kill 8139too kernel thread (sorta)
Date
Jeff Garzik <jgarzik@pobox.com> wrote:
>
> + if ((tp->time_to_die == 0) &&
> + (rtnl_lock_interruptible() == 0)) {
> rtl8139_thread_iter (dev, tp, tp->mmio_addr);
> rtnl_unlock ();
> }
>
> - complete_and_exit (&tp->thr_exited, 0);
> + if (tp->time_to_die == 0)
> + schedule_delayed_work(&tp->thread, next_tick);
> }

...

> +static void rtl8139_stop_thread(struct rtl8139_private *tp)
> +{
> + if (tp->time_to_die < 0)
> + return;
> +
> + tp->time_to_die = 1;
> + wmb();
> +
> + if (cancel_delayed_work(&tp->thread) == 0)
> + flush_scheduled_work();
> }

Race alert:

CPU0 CPU1
rtl8139_thread
rtnl_lock
rtl8139_thread_iter
rtnl_unlock
tp->time_to_die == 0
rtl8139_stop_thread
tp->time_to_die = 1
cancel_delayed_work == 0
flush_scheduled_work
schedule_delayed_work

So by the time rtl8139_stop_thread returns, the work is still scheduled.

The standard way to solve this is to get rid of the time_to_die check
in rtl8139_thread before the rescheduling and then use the horrible
cancel_rearming_delayed_workqueue function.

However, in this case it's much easier than that. Simply change
rtl8139_thread to do

rtnl_lock();
if (tp->time_to_die == 0) {
rtl8139_thread_iter(dev, tp, tp->mmio_addr);
schedule_delayed_work(&tp->thread, next_tick);
}
rtnl_unlock();

This is not racy because rtl8139_stop_thread is also run under the
RTNL. Furthermore, you don't need the interruptible version anymore
since you are no longer using kill to kill the thread.

This also fixes the bug that if you fail to acquire RTNL the Work
is delayed by another next_tick ticks.

Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
-
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/

\
 
 \ /
  Last update: 2005-10-31 21:53    [W:0.061 / U:0.112 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site