From: Ben Collins <bcollins@debian.org>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.5 Problem Report Status
Date: Tue, 22 Oct 2002 22:28:52 -0400 [thread overview]
Message-ID: <20021023022852.GK536@phunnypharm.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0210222038380.8594-100000@dad.molina>
> --------------------------------------------------------------------------
> open 21 Oct 2002 oops in ieee1394
> 74. http://marc.theaimsgroup.com/?l=linux-kernel&m=103519819428268&w=2
>
> --------------------------------------------------------------------------
Oh this is a real ass biter.
I have a workqueue that I setup once. Same data, same function, it never
changes. Every so often I call schedule_work() for the task.
Is queue_task() not reentrant? IOW, can I not schedule work that was
already scheduled similar to how tasklets worked?
Also, after the task has been run, does the workqueue struct's list
member not get cleared?
I'm a bit confused by this, as I expected behavior similar to before.
Ben
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo - http://www.deqo.com/
next prev parent reply other threads:[~2002-10-23 2:22 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 2:07 2.5 Problem Report Status Thomas Molina
2002-10-23 2:28 ` Ben Collins [this message]
2002-10-23 2:43 ` Ben Collins
2002-10-23 7:58 ` Russell King
2002-10-23 9:53 ` jbradford
2002-10-23 10:35 ` Vojtech Pavlik
2002-10-23 12:21 ` jbradford
2002-10-23 12:26 ` jbradford
2002-10-23 13:09 ` Alan Cox
2002-10-23 14:14 ` jbradford
2002-10-23 15:25 ` Alan Cox
2002-10-23 15:31 ` jbradford
2002-10-23 17:03 ` Patrick Mochel
2002-10-23 17:34 ` Alan Cox
2002-10-26 14:18 ` Toon van der Pas
2002-10-26 19:06 ` Patrick Mochel
2002-10-23 14:29 ` erik
2002-10-23 13:41 ` caligula
2002-10-31 15:16 ` caligula
-- strict thread matches above, loose matches on Subject: below --
2002-10-31 17:01 Kent Yoder
2002-10-23 2:26 Grover, Andrew
[not found] <Pine.LNX.4.44.0210120758420.4532-100000@dad.molina>
2002-10-12 16:51 ` jbradford
2002-10-13 21:54 ` Stig Brautaset
2002-10-05 20:21 Mikael Pettersson
2002-10-05 22:10 ` Thomas Molina
2002-10-05 23:19 ` John Levon
2002-10-05 18:18 Steven Cole
2002-10-05 16:57 Thomas Molina
2002-10-05 17:19 ` Bjoern A. Zeeb
2002-10-05 17:38 ` Thomas Molina
2002-10-05 18:05 ` Robert Love
2002-10-06 20:13 ` Gcc k6 testing account
2002-09-21 22:52 Thomas Molina
2002-09-21 22:52 ` William Lee Irwin III
2002-09-21 23:26 ` Axel Siebenwirth
2002-09-18 8:39 Thomas Molina
2002-09-17 1:57 Thomas Molina
2002-09-17 12:37 ` Helge Hafting
2002-09-17 20:58 ` Thomas Molina
2002-09-17 20:48 ` William Lee Irwin III
2002-09-04 3:26 Thomas Molina
2002-09-04 3:43 ` Andre Hedrick
2002-09-04 3:52 ` Robert Love
2002-09-04 8:08 ` Axel H. Siebenwirth
2002-09-04 10:16 ` Thomas Molina
2002-08-19 0:25 2.5 Problem Report status Thomas Molina
2002-08-10 18:09 2.5 Problem Report Status Thomas Molina
2002-08-22 19:29 ` James Simmons
2002-07-26 15:18 Thomas Molina
2002-07-27 20:04 ` James Simmons
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=20021023022852.GK536@phunnypharm.org \
--to=bcollins@debian.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox