https://bugzilla.novell.com/show_bug.cgi?id=409504
User teheo@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=409504#c3
--- Comment #3 from Tejun Heo 2008-07-28 00:45:40 MDT ---
Hmmm.... Whether a mmc device can be opened r/w or not is determined at open
time in cdrom_open_write(). The code has been quite stable and I don't really
know why or how they got shaped into the current form, but the traditional
writable semantics doesn't always fit. DVD RAM device is writable alright but
is a recorded re-writable media writable or not? ie. A recording program would
want to open the device RW, issue blank command followed by writes but other
programs which blindly issue writes without blanking will fail. Writing to MMC
devices is pretty complex and I suppose that's why the kernel tries to be
permissive and let the users decide as the kernel doesn't know much about
writing anyway. Writing is usually between the drive firmware and userland
burning app. Another example would be a partially written media which a
knowledgeable burning app can append new sessions but dumb WRITE(10)s would
just fail.
That said, the reported problem is pretty stinky. Maybe there needs to be a
distinction between randomly writable and recordable. Hmmm... How come the
'ro' flag doesn't work?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.