Re: PATCH: cdrecord: avoiding scsi device numbering for ide devices

[David Lang <david.lang@digitalinsight.com>]

I have burned one coaster in the last year with CDrecord (running as root) 
so it's still possible, it's just very rare.

David Lang

On Tue, 10 Aug 2004, Con Kolivas wrote:

> Date: Tue, 10 Aug 2004 08:59:25 +1000
> From: Con Kolivas <kernel@kolivas.org>
> To: Albert Cahalan <albert@users.sourceforge.net>
> Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>,
>     alan@lxorguk.ukuu.org.uk, dwmw2@infradead.org,
>     schilling@fokus.fraunhofer.de, axboe@suse.de
> Subject: Re: PATCH: cdrecord: avoiding scsi device numbering for ide devices
> 
> Albert Cahalan writes:
>
>
>> Joerg:
>>    "WARNING: Cannot do mlockall(2).\n"
>>    "WARNING: This causes a high risk for buffer underruns.\n"
>> Fixed:
>>    "Warning: You don't have permission to lock memory.\n"
>>    "         If the computer is not idle, the CD may be ruined.\n"
>> 
>> Joerg:
>>    "WARNING: Cannot set priority class parameters priocntl(PC_SETPARMS)\n"
>>    "WARNING: This causes a high risk for buffer underruns.\n"
>> Fixed:
>>    "Warning: You don't have permission to hog the CPU.\n"
>>    "         If the computer is not idle, the CD may be ruined.\n"
>
> Huh? That can't be right. Every cd burner this side of the 21st century has 
> buffer underrun protection. I've burnt cds _while_ capturing and encoding 
> video using truckloads of cpu and I/O without superuser privileges, had all 
> the cdrecord warnings and didn't have a buffer underrun. Last time I gave 
> superuser privilege to cdrecord it locked my machine - clearly it wasn't 
> rt_task safe.
>
> Con
>
> -
> 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/
>

-- 
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan