From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: linux-hotplug@vger.kernel.org
Subject: Re: [GIT] Experimental threaded udev
Date: Tue, 02 Jun 2009 09:13:58 +0000 [thread overview]
Message-ID: <4A24ED56.2010806@tuffmail.co.uk> (raw)
In-Reply-To: <4A1EA138.10400@tuffmail.co.uk>
Kay Sievers wrote:
> On Mon, Jun 1, 2009 at 15:57, Kay Sievers <kay.sievers@vrfy.org> wrote:
>
>
>>> The code looked like you freed the worker, but left the event RUNNING, and
>>> it would never be released. I would delete the event instead, just like the
>>> old system.
>>>
>>> I haven't read V2 yet though, maybe you fixed it.
>>>
>> I just set it back to QUEUED for now. Not sure if droppin git or
>> re-trying it a few times would be better.
>>
>
> Version 3, which should clean up events with a worker that died. Also
> kills all workers if the config has changed.
>
For strict correctness, I guess we need to do the same for "udevadm
control --log-priority" and "udevadm control --env".
Hmm, it says worker_kill_idle(). If there are running events at the
time, their stale workers will survive. At the moment kill(worker->pid,
SIGTERM) allows the current event to finish before it terminates, so one
solution would be to just kill all the workers.
Regards
Alan
next prev parent reply other threads:[~2009-06-02 9:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 14:35 [GIT] Experimental threaded udev Alan Jenkins
2009-05-28 15:09 ` Kay Sievers
2009-05-28 15:39 ` Alan Jenkins
2009-05-29 17:53 ` Alan Jenkins
2009-05-29 18:11 ` Kay Sievers
2009-06-01 2:41 ` Kay Sievers
2009-06-01 9:29 ` Alan Jenkins
2009-06-01 11:32 ` Kay Sievers
2009-06-01 12:33 ` Kay Sievers
2009-06-01 13:30 ` Kay Sievers
2009-06-01 13:46 ` Alan Jenkins
2009-06-01 13:57 ` Kay Sievers
2009-06-01 16:22 ` Kay Sievers
2009-06-01 16:24 ` Alan Jenkins
2009-06-01 19:39 ` Kay Sievers
2009-06-02 4:58 ` Kay Sievers
2009-06-02 9:13 ` Alan Jenkins [this message]
2009-06-02 9:26 ` Alan Jenkins
2009-06-02 11:39 ` Kay Sievers
2009-06-02 14:05 ` Kay Sievers
2009-06-03 19:44 ` Kay Sievers
2009-06-03 20:46 ` Alan Jenkins
2009-06-03 22:20 ` Kay Sievers
2009-06-03 23:53 ` Kay Sievers
2009-06-06 14:20 ` Kay Sievers
2009-06-06 17:01 ` Bryan Kadzban
2009-06-08 11:45 ` Scott James Remnant
2009-06-08 16:29 ` Bryan Kadzban
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=4A24ED56.2010806@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--cc=linux-hotplug@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.