public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian King <brking@us.ibm.com>
To: Chris Wright <chrisw@osdl.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	Srivatsa Vaddagiri <vatsa@in.ibm.com>
Subject: Re: [PATCH] Use workqueue for call_usermodehelper
Date: Wed, 21 Apr 2004 08:42:02 -0500	[thread overview]
Message-ID: <40867A2A.9070709@us.ibm.com> (raw)
In-Reply-To: 20040419113854.H22989@build.pdx.osdl.net

Chris Wright wrote:
> * Rusty Russell (rusty@rustcorp.com.au) wrote:
> 
>>[ Vatsa, this should solve your NUMA+HOTPLUG_CPU deadlock too, I think ]
>>
>>This uses the create_singlethread_workqueue() function presented in the
>>last patch, although it could just as easily use create_workqueue().
> 
> 
> Nice, this seems like it should fixup the problem Brian was seeing too,
> and maintain return code from kernel_thread(), etc. instead of the async
> option.  Brian, did you give these changes a whirl? (they're in latest
> -mm tree)

I tried out the fix on my system and it seemed to work fine. However, I
am having trouble recreating the deadlock with old code now that my
system has been reconfigured...

-Brian


-- 
Brian King
eServer Storage I/O
IBM Linux Technology Center


      reply	other threads:[~2004-04-21 13:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19  3:36 [PATCH] Use workqueue for call_usermodehelper Rusty Russell
2004-04-19 18:38 ` Chris Wright
2004-04-21 13:42   ` Brian King [this message]

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=40867A2A.9070709@us.ibm.com \
    --to=brking@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=chrisw@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=torvalds@osdl.org \
    --cc=vatsa@in.ibm.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