mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Tejun <htejun@gmail.com>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] add execute_in_process_context() API
Date: Wed, 08 Feb 2006 09:36:33 -0600	[thread overview]
Message-ID: <1139412994.3003.10.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <43EA0E7D.3030302@gmail.com>

On Thu, 2006-02-09 at 00:30 +0900, Tejun wrote:
> I haven't really looked at the code carefully, but I think one work 
> struct + atomic counter (say pending_reap_cnt) should do it. 
> queue_work() guarantees the work is run at least once after the call, so 
> bumping pending_reap_cnt and queueing the work in target reap and 
> reaping pending_reap_cnt times in the work should work.

Actually, no, unfortunately that doesn't work (and I did actually try
it).  The problem is that the target_reap actually removes the target
from the sysfs namespace.  So, if the reap is still pending but you
cannot find the target, you'll allocate one, but then you may be racing
to add it to the namespace (i.e. a quick succession of scsi
remove-single-device followed by scsi add-single-device of the same
H/C/T/L shows this).  If you lose the race, the add fails because the
namespace is already occupied.  And, unfortunately, the device_del that
does the namespace removal requires user context ...

James



  reply	other threads:[~2006-02-08 15:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1139342419.6065.8.camel@mulgrave.il.steeleye.com.suse.lists.linux.kernel>
2006-02-08  8:06 ` Andi Kleen
2006-02-08  8:18   ` Andrew Morton
2006-02-08  8:50     ` Andi Kleen
2006-02-08 15:15   ` James Bottomley
2006-02-08 15:18     ` Andi Kleen
2006-02-08 15:57       ` James Bottomley
2006-02-08 16:07         ` Andi Kleen
2006-02-08 15:30     ` Tejun
2006-02-08 15:36       ` James Bottomley [this message]
2006-02-07 20:00 James Bottomley
2006-02-07 20:26 ` Dave Jones
2006-02-07 20:34   ` Andrew Morton
2006-02-08 12:51 ` Stefan Richter

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=1139412994.3003.10.camel@mulgrave.il.steeleye.com \
    --to=james.bottomley@steeleye.com \
    --cc=ak@suse.de \
    --cc=htejun@gmail.com \
    --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

Powered by JetHome