lkml.org 
[lkml]   [2004]   [Aug]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.6.8.1 Mis-detect CRDW as CDROM
On Mon, 16 Aug 2004, Marc Ballarin wrote:

> Here are the additional commands I permit right now. It allows me to blank
> a CDRW and record in TAO mode. k3b needs MODE_SELECT_10 even
> for read-only access.
>
>
>
> safe_for_read(GPCMD_GET_CONFIGURATION),
> safe_for_read(GPCMD_GET_PERFORMANCE),
> safe_for_read(MODE_SELECT_10),
>
> safe_for_write(ALLOW_MEDIUM_REMOVAL),
> safe_for_write(REZERO_UNIT),
> safe_for_write(SYNCHRONIZE_CACHE),
> safe_for_write(GPCMD_SET_SPEED),
> safe_for_write(GPCMD_SEND_OPC),
> safe_for_write(GPCMD_BLANK),
> safe_for_write(GPCMD_CLOSE_TRACK),
> safe_for_write(0x5c), //whatever this might be

Read Buffer Capacity
>
> Shouldn't most GPCMD_* commands be safe for reading or writing, at least
> for CD devices?
> Are commands like MODE_SELECT_10 really safe for read?
>
Mode Select is not safe enough even for write (i.e., CAP_RAWIO must be
required). Is it really necessary for Mode Select to succeed or do the
applications just try to do something and fail gracefully?

--
Kai
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:05    [W:0.089 / U:0.480 seconds]
©2003-2014 Jasper Spaans. Advertise on this site