Rick Troth wrote: > Lock the file. > Or have the device driver enforce single access. But why lock? CP can handle multiple parralel diag8 calls from different processors just fine, and if the Linux userspace interface is done proper there is no race-issue at all.
File locking is limited to super user "root" versus the existing implementation allows root to specify who can issue CP commands [default: only root is allowed to issue CP commands]. And what if a malfunctioning program does flock() and then ends up in an endless loop? That would leave the file locked and the diag8 service would be unavailable. All those issues don't exist with the current implementation. -- Carsten Otte IBM Linux technology center ARCH=s390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
