linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: Accessing device information in REMOVE agent
Date: Sun, 09 Nov 2003 10:06:13 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-106837323001259@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106829667618187@msgid-missing>

On Sunday 09 November 2003 01:25, Greg KH wrote:
> On Sat, Nov 08, 2003 at 04:02:25PM +0300, Andrey Borzenkov wrote:
> > I'd like to be notified when block device goes away (e.g. USB stick
> > unplugged) basically to look if device is in use and possibly initiate
> > clean up. Block hotplug currently is passing only DEVPATH; but it alone
> > is not reliable way to identify it; device may be used under alias names
> > via symbolic links.
>
> What do you mean?  DEVPATH is unique for that point in time.  There are
> no alias's in sysfs.
>

Sorry I had to be more precise.

I'd like to (try to) replace current synchronous media change checks in 
supermount by mounting device on insert and releasing it on remove. For those 
cases when it makes sense of course, USB sticks in the first place.

But users are free to use any names or links for their device names i.e. they 
can do

ln -s sda /de/myflash
mount /dev/myflash

and on remove it is rather hard to match this name against DEVPATH. But I can 
save (major,minor) when mounting and use it to match mounted filesystem on 
remove.

>
> > Would it make sense to add device number? It seems to be natural native
> > "block device ID" :)
>
> What "device number"?  The major/minor?  Why?  It's about as unique as
> DEVPATH is for any point in time.
>

Hmm ... probably I can just as well use device name (meaning genhd->disk_name) 
you are right.

Thank you

-andrey



-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
_______________________________________________
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

  parent reply	other threads:[~2003-11-09 10:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-08 13:02 Accessing device information in REMOVE agent Andrey Borzenkov
2003-11-08 22:25 ` Greg KH
2003-11-09 10:06 ` Andrey Borzenkov [this message]
2003-11-09 19:50 ` Greg KH

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=marc-linux-hotplug-106837323001259@msgid-missing \
    --to=arvidjaar@mail.ru \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).