From: Rusty Russell <rusty@rustcorp.com.au>
To: Martin Diehl <lists@mdiehl.de>
Cc: NeilBrown <neilb@cse.unsw.edu.au>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org, akpm@zip.com.au
Subject: Re: [PATCH] Add module_kernel_thread for threads that live in modules.
Date: Mon, 16 Jun 2003 19:22:43 +1000 [thread overview]
Message-ID: <20030616092316.3E31B2C013@lists.samba.org> (raw)
In-Reply-To: Your message of "Mon, 16 Jun 2003 10:57:36 +0200." <Pine.LNX.4.44.0306161043020.2079-100000@notebook.home.mdiehl.de>
In message <Pine.LNX.4.44.0306161043020.2079-100000@notebook.home.mdiehl.de> you write:
> On Mon, 16 Jun 2003, Rusty Russell wrote:
> > It would be syncronous:
>
> You mean your cleanup_thread would block for completion of the keventd
> stuff? Ok, this would work. But then, when calling cleanup_thread, f.e. we
> must not hold any semaphore which might be acquired by _any_ other work
> scheduled for keventd or we might end in deadlock (like the rtnl+hotplug
> issue we had seen recently).
I think we're talking across each other: take a look at the existing
kernel/kmod.c __call_usermodehelper to see how we wait at the moment.
> > Also, this replaces complete_and_exit: the thread can just exit. This
> > simplifies things for the users, too...
>
> Personally I do like the complete_and_exit thing as a simple and clear
> finalisation point.
Not as clean as "wait until the thread has exited", surely!
Cheers,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2003-06-16 9:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 6:50 Rusty Russell
2003-06-16 7:58 ` Martin Diehl
2003-06-16 8:09 ` Rusty Russell
2003-06-16 8:57 ` Martin Diehl
2003-06-16 9:22 ` Rusty Russell [this message]
2003-06-16 10:27 ` Martin Diehl
2003-06-17 1:11 ` Rusty Russell
2003-06-16 8:19 ` Andrew Morton
2003-06-16 23:10 ` Neil Brown
2003-06-17 4:25 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2003-06-05 2:30 NeilBrown
2003-06-05 14:50 ` Andrey Klochko
2003-06-07 5:33 ` Neil Brown
2003-06-09 16:20 ` Andrey Klochko
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=20030616092316.3E31B2C013@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@mdiehl.de \
--cc=neilb@cse.unsw.edu.au \
--cc=torvalds@transmeta.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®