public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: David Zeuthen <david@fubar.dk>
To: James Bottomley <jejb@steeleye.com>
Cc: Matthew Wilcox <matthew@wil.cx>,
	Kay Sievers <kay.sievers@vrfy.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: scsi "target1:0:0"
Date: Tue, 16 Nov 2004 12:40:14 -0500	[thread overview]
Message-ID: <1100626815.4546.12.camel@davidz> (raw)
In-Reply-To: <1100625933.2770.45.camel@mulgrave>

On Tue, 2004-11-16 at 11:25 -0600, James Bottomley wrote:
> On Tue, 2004-11-16 at 11:23, David Zeuthen wrote:
> > Please explain how you expect userspace to keep track of the device tree
> > and enforce policy if we don't get hotplug events for things in the
> > middle of the tree?
> 
> The full path to the device is part of the environment of the event. 
> Can't you simply parse this?
> 

I suppose that userspace can just ascent up the tree and ignore devices
inbetween instead of assuming that every device in the middle has a bus
or class? That would probably work, yeah.

> I'm already getting complaints in the other direction (too many SCSI
> hotplug events) from the large system people.  I'm really loth to
> introduce more simply as a convenience for a user space daemon.
> 
> Really, I think there should only be hot plug events from real entities
> (which, more often than not are only the leaf nodes of the sysfs trees).
> 

That makes sense to me. Which leads me to ask: are there any
documentation spelling out what userspace should expect and what sorts
of guarantees there is in general for sysfs ABI? That would be useful to
prevent situations like this.

Thanks,
David



  reply	other threads:[~2004-11-16 17:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-16 16:21 scsi "target1:0:0" Kay Sievers
2004-11-16 16:33 ` James Bottomley
2004-11-16 16:55   ` Kay Sievers
2004-11-16 17:10     ` Matthew Wilcox
2004-11-16 17:23       ` David Zeuthen
2004-11-16 17:25         ` James Bottomley
2004-11-16 17:40           ` David Zeuthen [this message]
2004-11-16 19:15         ` greg k-h

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=1100626815.4546.12.camel@davidz \
    --to=david@fubar.dk \
    --cc=jejb@steeleye.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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