From: Christoph Hellwig <hch@infradead.org>
To: Samphan Raruenrom <samphan@nectec.or.th>
Cc: Jens Axboe <axboe@suse.de>, 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 14:58:21 +0100 [thread overview]
Message-ID: <20030826145821.A26398@infradead.org> (raw)
In-Reply-To: <3F4B44C2.4030406@nectec.or.th>; from samphan@nectec.or.th on Tue, Aug 26, 2003 at 06:30:10PM +0700
On Tue, Aug 26, 2003 at 06:30:10PM +0700, Samphan Raruenrom wrote:
> >>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.
if you are doing the unmount currently and nothing changes because
you hold the nessecary locks, yes. But as soon as you drop the locks
this is void. There's no way to find out whether you can unmount
a filesystem except trying it.
> 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.
See Jens' post.
next prev parent reply other threads:[~2003-08-26 14:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-25 18:22 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 ` [Rdi1] " Samphan Raruenrom
2003-08-26 11:36 ` Jens Axboe
2003-08-26 12:44 ` Samphan Raruenrom
2003-08-26 14:16 ` Jens Axboe
2003-08-26 13:58 ` Christoph Hellwig [this message]
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=20030826145821.A26398@infradead.org \
--to=hch@infradead.org \
--cc=axboe@image.dk \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=rdi1@opentle.org \
--cc=samphan@nectec.or.th \
/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
all inboxes | Powered by JetHome®