"logical unit communication failure" c2scan NEC ND-4550A 1.07
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): 43EB1F64.nail7GZ11H1SY@burner
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): 43EE6FF6.nailKBD11GI1Z@burner
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): 43F09AB1.nailKUSM1KY4M@burner
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): 43F0A8CE.nailKUS1410VN7@burner
Joerg Schilling schrieb am 2006-02-13:
Quoted 6 lines
Quoted 4 lines · Matthias Andree
Joerg Schilling schrieb am 2006-02-13:
Quoted 2 lines
Filtering SCSI commands was an unannounced change of the interface that needs to be called a bug. I still do not see any fix for this.
You don't need a fix for the status quo, as shown before and below.
Quoted 4 lines
Quoted 2 lines
SCSI commands are not filtered for processes with RAWIO capability, which root processes have by default.
It seems that you did loose contact to reality :-(
Have you ever read /usr/src/linux/block/scsi_ioctl.c?
You should pay particular attention to the verify_command() function.
Quoting Linux 2.6.15.4 (you won't understand this, but that doesn't matter, the rest of the world knows I can prove my point, unlike you):
/* And root can do any command.. */
if (capable(CAP_SYS_RAWIO))
return 0;
if (!type) {
cmd_type[cmd[0]] = CMD_WARNED;
printk(KERN_WARNING "scsi: unknown opcode 0x%02x\n", cmd[0]);
}
/* Otherwise fail it with an "Operation not permitted" */
return -EPERM;This is taken from block/scsi_ioctl.c's verify_command(), ll. 204ff.
Quoted 1 line
Try to inform yourself about the problems or stay quiet.
Yeah right, I'll shut up because some guy with scruffy manners comes along and tells everybody they were stupid. Dream on.
Quoted 6 lines
Quoted 2 lines
The recommended installation on Linux is still setuid, so any claims cdrecord were affected are hypocritical.
Wrong again, check the recent workarounds in libscg/cdrecord to understand that the problem was not fixed in the Linux kernel but I introduced a workaround.
Which function should I look at?
Quoted 8 lines
Quoted 2 lines
Plus, you have been offered by Linux developers to send a list of commands that need to be allowed, you have not accepted that offer.
Are you really so ignorant?
I did tell people how to extract such a list _and_ I told them that such a list is subject to daily changes in case a new drive needs new SCSI commands.
You want them to do you a favor, so you get to show them the list they asked for. If you don't, you aren't getting anything. You can stomp your foot on the ground, cry out loud, shout your frustration from the rooftops, it isn't going to change the kernel, you know.
Signature · 1 line
Matthias Andree
IGNORE: "logical unit communication failure" c2scan NEC ND-4550A 1.07
Please accept my apologies for misdirecting the other thread on lk, it was supposed to go to cdwrite at other.debian.org (where I resent it).
Signature · 1 line
Matthias Andree