Hi,
if
open("/dev/sr0", O_RDONLY);
pulls in the tray of an optical drive, it immediately returns -1 with
errno ENOMEDIUM, or the first read(2) fails with EIO. Later, when the
drive has stopped blinking, another open() yields success and read()
works.
This affects not only userland reading of the device file but also
mounting the device.
The fundamental problem of the current implementation is that function
sr_block_open() does medium assessment before calling cdrom_open(), under
which open_for_data() performs the tray loading too late.
A minor problem is that there is currently no waiting loop for the drive's
decision about the medium.
Please regard my proposal as follow-up to commit 2bbea6e11735 ("cdrom: do
not call check_disk_change() inside cdrom_open()") of march 2008. It moved
medium assessment out ouf cdrom_open() but left behind tray loading.
--------------------------------------------------------------------------
For now my proposal fixes only data reading via sr, because that's what i
am able to test:
Factor out from open_for_data() a new function cdrom_handle_open_tray()
and export it.
It decides whether it can and should load the tray. If so, it emits the
tray loading command and waits for up to 40 seconds for the drive to make
its decision. Plus 1 second of waiting in case of a usable medium, in
order to avoid hard-to-test narrow race conditions.
Let cdrom_open() not attempt to load the tray any more, but rather just
return -ENOMEDIUM if it detects an open tray.
Let sr_block_open() call cdrom_handle_open_tray() under mutex cd->lock
which it gives up immediately thereafter.
Then it calls the same sequence of medium assessment, mutex cd->lock and
cdrom_open() as it does currently.
Thanks to commit 51a858817dcd ("scsi: sr: get rid of sr global mutex") of
february 2020, the blocking of at most 41 seconds only affects the
particular drive and not all other sr devices.
-----------------------------------------------------------------------
Successful tests:
I tested with 3 different drives at SATA and USB (ASUS DRW-24D5MT,
Pioneer BDR-S09, LG BH16NS40 in USB box) simultaneously by
time dd if=/dev/sr"$N" bs=2048 count=1 of=/dev/null
with CD, DVD, and BD media. Waiting times ranged from 9 to 23 seconds.
The same times were measured when each drive was the only busy one.
Simultaneous full reads succeeded starting from open tray by
time dd if=/dev/sr"$N" bs=2048 status=progress of=/dev/null
I tested mounting CD, DVD and BD with ISO 9660 from open tray by
mount /dev/sr"$N" /mnt/iso
To make sure that no unwanted tray loading happens, i tested with open
tray by a program which prevents loading by O_NONBLOCK:
fd = open(path, O_RDONLY | O_NONBLOCK);
ret = ioctl(fd, CDROMREADTOCHDR, &hdr);
The open() call succeeds, whereas the ioctl() fails with ENOMEDIUM.
The tray does not move.
The patches were checked on Debian 10 by
./scripts/checkpatch.pl --strict --codespell --codespellfile \
/usr/lib/python3/dist-packages/codespell_lib/data/dictionary.txt
---------------------------------------------------------------------
Patch version:
v2 is based on git://git.kernel.dk/linux-block branch for-next to take
into respect commit afd35c4f573d ("sr: use bdev_check_media_change") and
commit 38a2b557e238 ("sr: simplify sr_block_revalidate_disk").
Newest in the branch was commit 73f2e37b498a ("Merge branch
'for-5.10/drivers' into for-next").
v2 improves the concurrency behavior of its tray loader with competing
tray loading by the human user. v1 reported "no medium" when encountering
a drive which is already in the process of decision. v2 waits for this
decision.
--------------------------------------------------------------------
The rest of this mail is about these aspects:
- What about CD audio and non-sr CD drivers.
- Why not (yet) waiting without mutex after tray loading.
- Why i can only test data reading via sr.
- Why the current code not always yields ENOMEDIUM at open() but sometimes
EIO at the first read(2).
--------------------------------------------------------------------
What about CD audio and non-sr CD drivers:
Because i lack of testing opportunities (see below), i omit:
- Calling cdrom_handle_open_tray() in the bdops.open() functions of
cdrom/gdrom.c, block/paride/pcd.c, ide/ide-cd.c.
- Calling cdrom_handle_open_tray() in the callers of
check_for_audio_disc(): cdrom_ioctl_audioctl() and
cdrom_ioctl_play_trkind() which control audio playback by the drive to
some (traditionally analog) audio outlet.
- Replacing the tray loading code of check_for_audio_disc() in cdrom.c
by a mere status checker like by my proposal in open_for_data().
(It could stay in place but would be of no use any more.)
My changes in sr_block_open() and open_for_data() could serve as
templates for these omitted tasks.
I would prepare patches if there is acceptance for untested code.
--------------------------------------------------------------------
Why not (yet) waiting without mutex after tray loading:
The automatic tray loading happened under the mutex for cdrom_open().
My proposal upholds this locking by acquiring cd->lock before calling
cdrom_handle_open_tray() and giving it up before medium assessment.
It seems to me that it should be safe to run the new function
cdrom_handle_open_tray() without cd->lock, as it mainly emits drive
commands START/STOP UNIT and TEST UNIT READY. It does not manipulate
members of device structs.
Without lock it would enable access to the drive by other threads during
the waiting for a drive decision.
But i have no idea how to prove that it is safe.
---------------------------------------------------------------------
Why i can only test data reading via sr:
None of my DVD and BD drives has a socket for plugging loudspeakers or
earphones. So i cannot test the consequences of my proposal to the ability
of playing audio tracks.
sr is the only driver i can test, because of the extinction status of the
devices of the other drivers which call cdrom_open():
- gdrom seems to be for ancient gaming consoles. It is unclear to me
whether they could load a tray by own motor power.
- paride is described as ATAPI via an old printer cable.
- ide-cd ... was not that the CD part of hd swallowed by sr, as the HDD
part of hd was swallowed by sd ?
sr is well alive. BD drives cost ~80 EUR, 25 GB BD-RE media <1 EUR.
Not a competitor to HDD, but to USB sticks.
---------------------------------------------------------------------
Why the current code not always yields ENOMEDIUM at open() but sometimes
EIO at the first read(2):
A newly bought Pioneer BDR-S09 shows this behavior with the current code.
dd reports I/O error rather than no medium.
Inspection by libburn shows that it waits with its reply to START/STOP
UNIT until it has decided over the medium. The first following TEST UNIT
READY yields key=6, asc=28h, ascq=00h "Not Ready to Ready change, medium
may have changed" and the second TEST UNIT READY yields success.
This substitutes for the missing waiting loop, but not for the lack of
medium assessment after loading. So open(2) succeeds, but read(2) faces
the medium assessment which was made when the tray was out. The result was
in my experiments always EIO on the first read().
This behavior is peculiar among my drives. Seven others reply to
START/STOP UNIT as soon as the tray has moved in. Then for several seconds
they reply to TEST UNIT READY by key=2, asc=04h, ascq=01h "Logical unit is
in process of becoming ready".
Have a nice day :)
Thomas
Thomas Schmitt (2):
cdrom: delegate automatic CD tray loading to callers of cdrom_open()
sr: fix automatic tray loading for data reading
drivers/cdrom/cdrom.c | 173 +++++++++++++++++++++++++++++++-----------
drivers/scsi/sr.c | 12 ++-
include/linux/cdrom.h | 3 +
3 files changed, 141 insertions(+), 47 deletions(-)
--
2.20.1
