All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Inhibiting plug and play
Date: Tue, 18 Jun 2013 17:55:17 +0000	[thread overview]
Message-ID: <20130618175517.GA3689@kroah.com> (raw)
In-Reply-To: <51C09CA5.6020902@ubuntu.com>

On Tue, Jun 18, 2013 at 01:45:09PM -0400, Phillip Susi wrote:
> Various tools, but most notably partitioners, manipulate disks in such
> a way that they need to prevent the rest of the system from racing
> with them while they are in the middle of manipulating the disk.
> Presently this is done with a hodge podge of hacks that involve
> running some script or executable to temporarily hold off on some
> aspects ( typically only auto mounting ) of plug and play processing.
>  Which one depends on whether you are running hal, udisks, udisks2, or
> systemd.
> 
> There really needs to be a proper way at a lower level, either udev,
> or maybe in the kernel, to inhibit processing events until the tool
> changing the device has finished completely.  The question is, should
> this be in the kernel, or in udev, and what should the interface be?

What events are you wishing to inhibit?  And who is in control of them?

thanks,

greg k-h

  reply	other threads:[~2013-06-18 17:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-18 17:45 Inhibiting plug and play Phillip Susi
2013-06-18 17:55 ` Greg KH [this message]
2013-06-18 18:03 ` David Zeuthen
2013-06-18 18:40 ` Phillip Susi
2013-06-18 18:59 ` David Zeuthen
2013-07-16 17:23 ` [systemd-devel] " Lennart Poettering
2013-07-16 17:35 ` Phillip Susi

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=20130618175517.GA3689@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --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.