From: kuznet@ms2.inr.ac.ru
Message-Id: <200308281317.RAA20747@dub.inr.ac.ru>
Subject: Re: tasklet_kill will always hang for recursive tasklets on a UP
To: nagendra_tomar@adaptec.com
Date: Thu, 28 Aug 2003 17:17:06 +0400 (MSD)
Cc: wa@almesberger.net, quade@hsnr.de, linux-kernel@vger.kernel.org
In-Reply-To: <Pine.LNX.4.44.0308262141480.1471-100000@localhost.localdomain> from "Nagendra Singh Tomar" at  =?ISO-8859-1?Q?=20=E1?=
	=?ISO-8859-1?Q?=D7=C7?= 26, 2003 09:47:35 
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1008
Lines: 26

Hello!

> Either the tasklet_kill hangs (which will happen on UP)

Never can happen, unless you are trying to call tasklet_kill
from softirq context, which is illegal.


> So I believe that at least one (to be precise, the last one called before 
> tasklet dies) tasklet_schedule is not honoured.

You cannot call tasklet_schedule while kill is called. As I said in previous
mail, preventing new schedules is responsibility of callers. tasklet struct
and control functions do not maintain any information about its state, it is
for client to handle this in his preferred way.

You are right when saying the name is misnomer. tasklet_kill does not kill,
it waits for the moment when tasklet becomes really dead after client
strangled it with his own hands.

Alexey
-
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/