From: Samphan Raruenrom <samphan@nectec.or.th>
To: Jens Axboe <axboe@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
Jens Axboe <axboe@image.dk>,
linux-kernel@vger.kernel.org, Linux TLE Team <rdi1@opentle.org>,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: [Rdi1] Re: [PATCH] Add MOUNT_STATUS ioctl to cdrom device
Date: Tue, 26 Aug 2003 18:30:10 +0700 [thread overview]
Message-ID: <3F4B44C2.4030406@nectec.or.th> (raw)
In-Reply-To: <20030826095830.GA20693@suse.de>
Jens Axboe wrote:
> On Tue, Aug 26 2003, Christoph Hellwig wrote:
>>On Tue, Aug 26, 2003 at 04:09:54PM +0700, Samphan Raruenrom wrote:
>>>The only visible feature of this new magicdev is that now
>>>GNOME users can eject there CDs (the discs' icon will
>>>disappear). The eject button now act as 'umount' command.
>>>One new requirement from this new magicdev is the question
>>>"will umount failed?". I have no preference on any way to
>>>implement it. Should there be the right way to do it, I'll
>>>do so. I can think of many way to implement it (including
>>>adding a new lazy-lock mode to cdrom device) but since
>>>I have no kernel hacking experience, I need everyone
>>>advices. Novice users need this 'eject' button after all.
>>This doesn't make sense at all. Just try the unmount and
>>tell the user if it failed - you can't say whether it will
>>fail before trying.
Yes, you can! Reading the code, if vfsmount.mnt_count > 1 then
umount on that device will fail. Similar function is used
by autofs, i.e. may_umount() in fs/namespace.c. I know the patch
is not beautiful but it work.
Hmm. You seem to advice me to detect the 'eject' button then issue
a umount? I don't know how and I guess it is impossible. But maybe
I'm wrong.
> Exactly. You poll media events from the drive, and upon an eject request
> you try and umount it. If it suceeds, you eject the tray.
No, it seems impossible to sense the eject request (right?). This
is what I really did with the patched kernel and patched magicdev.
When, for example:-
- user insert CD
- magicdev sense the CD, mount /dev/cdrom -> eject is ok
- user play an mp3 file in the disc
- magicdev found MOUNT_STATUS=BUSY, lock the drive -> eject disabled
- user stop using any file on the disc
- magicdev found MOUNT_STATUS=MOUNTED, unlock the drive -> eject is ok
- user push the eject button, the disc pop out because it's not locked.
- magicdev sense empty drive, umount /dev/cdrom
--
Samphan Raruenrom,
The Open Source Project,
National Electronics and Computer Technology Center,
National Science and Technology Development Agency,
Thailand.
next prev parent reply other threads:[~2003-08-26 11:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-25 18:22 [PATCH] Add MOUNT_STATUS ioctl to cdrom device Samphan Raruenrom
2003-08-25 18:50 ` Christoph Hellwig
2003-08-26 6:50 ` Samphan Raruenrom
2003-08-26 7:32 ` Christoph Hellwig
2003-08-26 9:09 ` Samphan Raruenrom
2003-08-26 9:56 ` Christoph Hellwig
2003-08-26 9:58 ` Jens Axboe
2003-08-26 11:30 ` Samphan Raruenrom [this message]
2003-08-26 11:36 ` [Rdi1] " Jens Axboe
2003-08-26 12:44 ` Samphan Raruenrom
2003-08-26 14:16 ` Jens Axboe
2003-08-26 13:58 ` Christoph Hellwig
2003-08-26 15:32 ` Samphan Raruenrom
2003-08-26 15:45 ` Jens Axboe
2003-08-25 20:03 ` viro
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=3F4B44C2.4030406@nectec.or.th \
--to=samphan@nectec.or.th \
--cc=axboe@image.dk \
--cc=axboe@suse.de \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=rdi1@opentle.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.