All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott James Remnant <scott@ubuntu.com>
To: Alasdair G Kergon <agk@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
	linux-hotplug-devel@lists.sourceforge.net
Subject: Re: [dm-devel] [PATCH] improve atomicity of device creation
Date: Tue, 11 Dec 2007 16:42:13 +0000	[thread overview]
Message-ID: <1197391333.25082.31.camel@quest> (raw)
In-Reply-To: <20071211162538.GR22311@agk.fab.redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 677 bytes --]

On Tue, 2007-12-11 at 16:25 +0000, Alasdair G Kergon wrote:

> On Tue, Dec 11, 2007 at 04:08:36PM +0000, Scott James Remnant wrote:
> > This is a patch we've written and applied in Ubuntu to improve the
> > atomicity of devmapper device creation somewhat, and avoid races with
> > udev.
>  
> BTW I won't be applying this upstream - these nodes are designed to be
> managed by libdevmapper not udev so it's not relevant.  I'm awaiting
> patches that have been promised to an agreed design that will provide
> for correct libdevmapper/udev integration without races/deadlocks etc.
> 
What is that agreed design?

Scott
-- 
Scott James Remnant
scott@ubuntu.com

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 278 bytes --]

-------------------------------------------------------------------------
SF.Net email is sponsored by: 
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php

[-- Attachment #3: Type: text/plain, Size: 226 bytes --]

_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  reply	other threads:[~2007-12-11 16:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-11 16:08 [PATCH] improve atomicity of device creation Scott James Remnant
2007-12-11 16:25 ` Alasdair G Kergon
2007-12-11 16:25   ` [dm-devel] " Alasdair G Kergon
2007-12-11 16:42   ` Scott James Remnant [this message]
2007-12-11 17:03     ` Alasdair G Kergon
2007-12-11 17:03       ` [dm-devel] " Alasdair G Kergon
2007-12-11 17:18       ` Scott James Remnant
2007-12-11 17:51         ` Kay Sievers
2007-12-11 17:51           ` Kay Sievers
2007-12-11 18:08           ` Alasdair G Kergon
2007-12-11 18:08             ` [dm-devel] " Alasdair G Kergon
2007-12-11 18:25             ` Kay Sievers
2007-12-11 18:25               ` Kay Sievers
2007-12-11 19:13               ` Alasdair G Kergon
2007-12-11 19:13                 ` [dm-devel] " Alasdair G Kergon
2007-12-11 19:43               ` Alasdair G Kergon
2007-12-11 19:43                 ` [dm-devel] " Alasdair G Kergon
2007-12-11 17:35 ` Kay Sievers
2007-12-11 17:35   ` Kay Sievers
2007-12-11 17:40   ` Scott James Remnant
2007-12-11 17:53     ` Alasdair G Kergon
2007-12-11 17:53       ` [dm-devel] " Alasdair G Kergon
2007-12-11 19:09       ` Scott James Remnant
2007-12-11 18:03     ` Kay Sievers
2007-12-11 18:03       ` [dm-devel] " Kay Sievers

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=1197391333.25082.31.camel@quest \
    --to=scott@ubuntu.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    /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.