From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Takashi Iwai <tiwai@suse.de>, Kay Sievers <kay@vrfy.org>
Cc: Jens Axboe <axboe@kernel.dk>, Oliver Neukum <oneukum@suse.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: How to fix CDROM/DVD eject mess?
Date: Tue, 03 Feb 2015 08:40:24 -0500 [thread overview]
Message-ID: <54D0CFC8.40305@gmail.com> (raw)
In-Reply-To: <s5h7fvzdvmi.wl-tiwai@suse.de>
[-- Attachment #1: Type: text/plain, Size: 651 bytes --]
On 2015-02-03 07:31, Takashi Iwai wrote:
>>> Then,
>>> udev unlocks the media and issues the SCSI eject ioctl unconditionally
>>> when DISK_EVENT_EJECT_REQUEST event is received. Since SCSI ioctl
>>> doesn't take the open refcount into account, it results in the
>>> forcible eject.
>>
>> Which again is the expected behavior in the user's view.
>
> What if user doesn't want? e.g. DVD/CD media is being burned?
>
FWIW, I have seen some drives where either the hardware or the drive
firmware ignores the eject button while a write operation is in progress
(ie, doesn't appear to even send the event, let alone eject the disk).
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2455 bytes --]
prev parent reply other threads:[~2015-02-03 13:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 13:20 How to fix CDROM/DVD eject mess? Takashi Iwai
2015-02-02 19:03 ` Kay Sievers
2015-02-02 19:34 ` Maciej W. Rozycki
2015-02-02 19:45 ` Kay Sievers
2015-02-02 21:12 ` Maciej W. Rozycki
2015-02-03 12:36 ` Takashi Iwai
2015-02-03 8:52 ` Oliver Neukum
2015-02-03 13:34 ` One Thousand Gnomes
2015-02-03 17:53 ` Theodore Ts'o
2015-02-02 20:02 ` Austin S Hemmelgarn
2015-02-02 20:53 ` Ondrej Zary
2015-02-03 12:31 ` Takashi Iwai
2015-02-03 13:39 ` One Thousand Gnomes
2015-02-03 13:49 ` Takashi Iwai
2015-02-03 13:40 ` Austin S Hemmelgarn [this message]
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=54D0CFC8.40305@gmail.com \
--to=ahferroin7@gmail.com \
--cc=axboe@kernel.dk \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oneukum@suse.de \
--cc=tiwai@suse.de \
/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.